> syncdb will not alter an existing database. Maybe the Django authors are obeying the DB ideal that if you could do without a field for the first few records, then that field, when it arrives, should be normalized out into its own table.
(Roughly speaking, a field with too many NULL or False entries is a candidate to be a child record.) Just recently I added to a SKU record a new boolean - MembersOnly - and I added it by creating a new table, whose only record is a sku_id. I did this because I didn't want to ask my colleagues if they wanted to run syncdb on a live database, and it seems I guessed right! But this sophistry won't help anyone when they have to run ALTER TABLE... (-: -- Phlip -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
