I guess there's nothing Django could do except perhaps throw a more helpful
error message. Feel free to submit a ticket and/or patch if you see any
value in that and if it seems feasible. I'm not sure about that offhand.
On Monday, December 12, 2016 at 8:57:09 PM UTC-5, Francis Fisher wrote:
>
So it turns out that a different user owned the non-managed tables, which
seemed to prevent the django user from accessing certain information about
those tables.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group
I can see why django is crashing at File
"/usr/local/lib/python2.7/dist-packages/django/db/backends/postgresql/introspection.py",
line 178, in get_constraints
If I run the query at that line in postgres, I get the following response:
constraint_name|
The above migration crash was when applying to a postgres database, I've
tried applying this migration to a mysql database and it still crashes,
albeit differently.
--
File "evetools/manage.py", line 10, in
execute_from_command_line(sys.argv)
File
It could be a bug or your database might be in an inconsistent state
somehow. The next step would be to debug it a bit more and put together a
minimal project that reproduces the issue.
On Monday, December 12, 2016 at 4:45:55 PM UTC-5, Francis Fisher wrote:
>
> Any idea if I'm doing something
Any idea if I'm doing something wrong or if I'm running into a bug?
I added some fields to a model, and generated a migration.
When I apply the migration, the migrate command crashes, with both django
1.10.3 and 1.10.4.
I had a similar migration issue with another app in the same project, that
6 matches
Mail list logo
