#15633: Bad documentation of post_syncdb signal
------------------------------------+-------------------------------
Reporter: vzima | Owner: nobody
Type: Bug | Status: new
Milestone: | Component: Documentation
Version: SVN | Severity: Normal
Resolution: | Keywords:
Triage Stage: Accepted | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
------------------------------------+-------------------------------
Comment (by vzima):
Replying to [comment:7 aaugustin]:
> Regarding your second point, there's already a solution for this
problem, see https://docs.djangoproject.com/en/dev/howto/initial-data
/#providing-initial-sql-data
This does not work one would expected from documentation.
If I create initial SQL like
{{{
ALTER TABLE "some_table"
ADD CONSTRAINT "some_table_constraint1" CHECK (some_column = 45);
}}}
This will make `flush` command fail, as it emits `post_syncdb` signal
marking that table is created (but it is not). This can be sometimes
prevented using `IF NOT EXISTS` condition, but not always.
--
Ticket URL: <https://code.djangoproject.com/ticket/15633#comment:8>
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 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.
