On 7/17/07, Manoj Govindan <[EMAIL PROTECTED]> wrote: > > Hi Russ, > > Quote: initial_data is intended for data that must _always_ be in your > database. > > Shouldn't developers have the option to run syncdb without loading > initial_data? For example: a model has changed and the developer > merely wishes to synchronize the database without loading any data.
If there are times that you don't want to load the data, then it isn't initial data. Put it in a different fixture, and load it when you need it. However, the installation of initial_data should possibly be a little more selective; i.e., only installing data for a model that has just been added to the database, rather than all initial data every time. In general practice, this won't make much of a difference, since you generally only call syncdb once when installing a finished application. However, I suppose it could cause some confusion during development if re-installing initial data for application A overwrites changes that have been made since model A was first installed. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
