#11074: syncdb should execute custom field SQL separately from initial model SQL
-------------------------------------+-------------------------------------
Reporter: psmith | Owner: nobody
Type: Bug | Status: closed
Component: Core (Management | Version: 1.0
commands) | Resolution: fixed
Severity: Normal | Triage Stage: Accepted
Keywords: syncdb geodjango | Needs documentation: 0
post_create_sql | Patch needs improvement: 0
Has patch: 1 | UI/UX: 0
Needs tests: 1 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by aaugustin):
* status: new => closed
* resolution: => fixed
Comment:
With the new migrations framework, you must use a RunSQL operation in a
migration instead of custom SQL.
As a consequence this issue is resolved in Django 1.7.
--
Ticket URL: <https://code.djangoproject.com/ticket/11074#comment:5>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.f4623addccbdf0e34ee3b6feb28cea03%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
