Hi,
We've been hitting this issue as well in our environment - so far we've
been able to workaround this by using fake migrations but that is not
long lasting solution.
We're using Oracle as our database backend and we have hundreds of
legacy databases which aren't unified at their schema but there are some
little differences here and there.
Now, when Django creates migrations it does them "wrong". Oracle doesn't
have concept of transactioned DDL, but Django assumes every backend does
- thus it automatically creates migrations so that it squashes all
migrations done since last migration to one. And that causes the
problem. With Oracle each migration should be individually runnable so
if one crashes it can't leave database in unknown state.
For example if my migration adds column in tables A, B and C. If A
success but B fails in Oracle it means that even migration failed A got
applied requiring manual work to also roll back manually those changes.
So, instead of Django migrations we decided to go with liquibase for
database migrations since it has better workflow and concepts for
migrations in Oracle.
For us this feature would be really useful, by some mean to turn off
whole migration system. Personally I don't mind that if we had to do
some slight extra work (like app config stuff which was proposed) to
make it happen.
On 02.08.2017 21:30, Tim Graham wrote:
Perhaps giving some actionable, constructive feedback would be more
useful.
On Tuesday, August 1, 2017 at 6:50:47 PM UTC-4, Robert F. wrote:
I know this is an old topic but I completely agree with Frank.
Nothing gives me more headaches and makes me want to move off
Django more than migrations. They seldom run smoothly and cause
me no end of headaches. I hate them!
On Friday, November 20, 2015 at 2:26:59 PM UTC-8, Frank Malina wrote:
RE: Carl Meyer
>> To my knowledge, out of the many hundreds of
>> thousands of Django users, you are the first and only one
to request a
>> way to turn off migrations entirely.
No he isn't, Django migrations are ridiculous waste of time,
never work and make me angry.
I work with Django from v0.96 and it never got in the way as
much as it does now.
--
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
<mailto:django-users+unsubscr...@googlegroups.com>.
To post to this group, send email to django-users@googlegroups.com
<mailto:django-users@googlegroups.com>.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/a93ba892-599a-4677-9895-cb88ce36b01d%40googlegroups.com
<https://groups.google.com/d/msgid/django-users/a93ba892-599a-4677-9895-cb88ce36b01d%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
--
Jani Tiainen
--
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 https://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/e34d2470-6186-11ed-5f94-094cf1b862d8%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
