#4528: Add DATABASE_PRE_SYNCDB to settings
----------------------------------------------------+-----------------------
Reporter: Johan Bergström <[EMAIL PROTECTED]> | Owner:
nobody
Status: new | Component:
Core framework
Version: SVN | Resolution:
Keywords: database_pre_syncdb sql syncdb | Stage:
Design decision needed
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
----------------------------------------------------+-----------------------
Comment (by ubernostrum):
Replying to [comment:2 George Vilches <[EMAIL PROTECTED]>]:
> If we're going allow modifications before all the sync activities, why
not just create a pre_syncdb signal. That way it won't be yet another
setting to clutter the 99% case, but people could easily add the
dispatcher to a management.py in their own app.
>
> Or, with the new management refactor, maybe a user should just add their
own command entirely, and have their command call the syncdb command?
I like both of these ideas. Feel like writing up an implementation of one
of them?
--
Ticket URL: <http://code.djangoproject.com/ticket/4528#comment:3>
Django Code <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
-~----------~----~----~----~------~----~------~--~---
