On 25 August 2015 at 18:44, Marcos Eliziario <marcos.elizia...@gmail.com> wrote:
Changing the database accidentally can be avoided simply by adjusting the > privileges of the database user django uses. It's not perfect. The connection requires write access and Django inserts some data automatically. But table-level grants can be a paritial solution. And still Django complains about unapplied migrations... The thing is, nobody ever requested that, it is not a popular feature > request, so, it is not there and won't be there unless someone contributes > with a solid patch and a solid case for this added complexity I would like to provide solid patch as a pull request, but I'm afraid that it will be rejected due to some kind of spirit, politics or something else. BR, Marcin -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAB2m7Cyn4rTb-8Y5QJynjhd4puYDVwNv4FaKay446J7W%3DvGUmw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
