"James Bennett" <[EMAIL PROTECTED]> writes: > On 5/11/07, Thomas Guettler <[EMAIL PROTECTED]> wrote: >> First I missing a way to sync the database with the model. The command >> syncdb has a bad name. It should be called initdb. But you can live >> without autosync: Redirect the output of sqlall to a file. Update model, >> redirect the output again, and then "diff old.sql new.sql" shows >> you what you need to execute in a sql shell (ALTER TABLE ... (ALTER|DROP|ADD) >> COLUMN ...) > > This is a frequently-asked-for feature, but to date no-one's stepped > up and produced a solid implementation of schema evolution with a > commitment to maintain it; unless someone's willing to write and > maintain quality code for it, it probably won't happen.
Yeah. Doing that is really hard because DJango supports a few different SQL environments. I'd be happy to commit to supporting PostgreSQL but the thought of writing code to support PG, MySQL, SQLLite and maybe others is terrifying. Something needs to be done though... or ongoing maintenance of Django apps is going to be really hard. Something else I'd like in this area is the ability to plugin "serializers" for models so when views are created or updated I can control en masse how that's done. I'm thinking some of the time I would like to have Django write stored procedures for me so that I can abstract some of the store changes into the SQL and manage it there. -- Nic Ferrier http://www.tapsellferrier.co.uk --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
