On 17/11/2015 12:33 PM, marcin.j.no...@gmail.com wrote:
I have no migration directories, so assuming that it would not help
It has just occurred to me that I don't have any unmanaged apps. Maybe
that is why it worked for me? I seem to remember you need to mark apps
as unmanaged to switch of
On 17/11/2015 12:33 PM, marcin.j.no...@gmail.com wrote:
Mike, thanks. Â I have no migration directories, so assuming that it
would not help.
I just checked and I tested that on 1.8.5
So maybe step 0 is to downgrade and step 4 is to upgrade again.
Cheers
Mike
Tim, also thanks. I've checke
Mike, thanks. I have no migration directories, so assuming that it would
not help.
Tim, also thanks. I've checked that django-dev discussion, but no updates
here.
I don't want to discuss again and again about kicking out useful tools.
It looks like reimplementing old commands is the only way.
For Django 1.9+, I don't think there's a built-in way to do so. Until that
feature makes its way into Django (if it ever does), it might not be
difficult to reimplement those commands to the extent that you need them as
a third-party app. See
https://groups.google.com/d/topic/django-developers/
On 17/11/2015 11:14 AM, marcin.j.no...@gmail.com wrote:
Hi!
After upgrade from 1.5 to 1.8.6 I'm trying to dump sql from models.
I'm not using django migrations, and my db_router does not allow for
migrations.
Try this ...
1. Rename all the migrations directories if they exist
2. $~python ma
Hi!
After upgrade from 1.5 to 1.8.6 I'm trying to dump sql from models.
I'm not using django migrations, and my db_router does not allow for
migrations.
Every "sql*" management command gives me nothing (empty output), where I'm
expecting generated SQL.
1. How can I dump tables and indices
6 matches
Mail list logo
