i've saw too that manage.py syncdb create tables out of order, disobeying the foreign keys, many to many tables, etc...
On 5/25/06, Siah <[EMAIL PROTECTED]> wrote: > > Thanks for the response adrian. > > Somehow I felt the result of Alter Table is not as efficient as > properly creating the table in the first place. If I'm incorrect, that > I think I am, your suggestion is actually very good and should make my > life more efficient. > > I guess if I go with above, I don't have to cry over 'init' again, and > thanks for the quick tutorial on install django_apps. > > In terms of broken pieces. My sqlall worked fine right now, but my > sqlclear generates something like this: > ... > ALTER TABLE "ss_accountinfo" DROP CONSTRAINT > "bill_address_id_referencing_ss_address_id"; > ... > > that gives me this error: > > ERROR: constraint "bill_address_id_referencing_ss_address_id" does not > exist > > Thanks, > Sia > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
