On Sun, 2008-11-23 at 22:22 -0800, sajal wrote: > thanks a lot.. that fixed it. > > Even after making the mess that i made, a syncdb solved the issue > keeping all my other data intact. > > I however have a related question. > > While modifying the existing classes, i.e. adding fields, i do the > "ALTER TABLE" by hand as suggested by > http://www.djangobook.com/en/1.0/chapter05/ > > Am I gonna run into trouble for this with auth or something else?
No, that will be fine. Altering the table via SQL is not a problem. It's at initial creation time that the extra stuff (registering with the content type app and the auth system) is done. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
