#15633: Bad documentation of post_syncdb signal ---------------------------+--------------------------- Reporter: vzima | Owner: nobody Status: new | Milestone: Component: Documentation | Version: SVN Keywords: | Triage Stage: Unreviewed Has patch: 0 | ---------------------------+--------------------------- Signal post_sycndb is badly documented: - documentation says that created_models is list, but emit_post_sync_signal is called with set when it is called from syncdb command. Surprisingly it is called with set from flush command, so there is probably error in code as well. - documentation suggests that post_syncdb signal is called only when table is created, so it looks like you can use it to change database structure (create contraints, triggers, ...) These SQL fail when yout post_sycndb handler is called from flush, because flush does not change database structure (except SQLs with 'IF NOT EXISTS'-like conditions). Documentation should noted that handlers of this signal should not change database structure and for such cases customize sql hack in syncdb should be used.
-- Ticket URL: <http://code.djangoproject.com/ticket/15633> 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 django-updates@googlegroups.com. To unsubscribe from this group, send email to django-updates+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-updates?hl=en.