#16882: Clarify in the doc why one should not use 'init_command' after initial
database creation
--------------------------------------+------------------------------------
Reporter: julien | Owner: nobody
Type: Cleanup/optimization | Status: closed
Component: Documentation | Version: 1.3
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by Tim Graham <timograham@…>):
In [8bea1a7e4eacfe311651eafb506ab1f4e7691feb]:
{{{
#!CommitTicketReference repository=""
revision="8bea1a7e4eacfe311651eafb506ab1f4e7691feb"
[1.4.X] Fixed #16882 - Clarified why one should not use 'init_command'
after initial database creation.
Backport of 9974069620 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/16882#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 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.
