On 24-Dec-06, at 9:01 AM, Aaron Jacobs wrote:
2. if you are not worried about data loss run sqlreset - or better,
drop the database, create it and run syncdb
3. if you alter a model, run sqlall, examine the out put to see what
statements django wants and put them in manually
These two are fine for a single developer's purposes, but what about
if you want to distribute your app to others? You'd have to come up
with some automated process, even if it's hand-coded.
each time you change your schema, you write the appropriate sql
script and give it to your users. This is what the django devels do
when they make backward incompatible changes.
--
regards
kg
http://lawgon.livejournal.com
http://nrcfosshelpline.in/web/
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
