#13868: Inability to create superuser during syncdb when using GIS fields in
AUTH_PROFILE_MODULE
---------------------------------+------------------------------------------
Reporter: jskitz | Owner: jbronn
Status: assigned | Milestone:
Component: GIS | Version: 1.2
Resolution: | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------+------------------------------------------
Changes (by jbronn):
* owner: nobody => jbronn
* status: new => assigned
Comment:
I'll accept the ticket for now, but I'm not sure if there will be a patch
acceptable for this edge-case scenario that has an easy work-around (run
`syncdb` first, and create the superuser afterwards):
{{{
$ ./manage.py syncdb --noinput
$ ./manage.py createsuperuser
}}}
From my brief review, the only way to fix this would be to change when the
`post_syncdb` is emitted, as it is done before the index creation SQL
(which is now where the `AddGeometryColumn` SQL is actually generated).
The side-effects of this 'fix' could be far-reaching have many backwards-
incompatible consequences, so for now I would recommend the workaround
given above.
--
Ticket URL: <http://code.djangoproject.com/ticket/13868#comment:2>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
