Solved : I dropped all the database tables (including the contib.auth ones) and ran syncdb, suddenly everything was fine. odd , but is working now . Jonathan
On Monday, June 4, 2012 11:27:44 AM UTC+3, xTalisman wrote: > > Bruno , > I thought so , so I deleted the the whole database (sqlite3) and ran the > syncdb again , it created the tables as defined by django.contrib.auth and > my application - but did not create the foreignkey columns manager and > users. > Any ideas ? > > On Monday, June 4, 2012 11:23:33 AM UTC+3, bruno desthuilliers wrote: >> >> On Jun 4, 9:49 am, xTalisman <jonathan.talis...@gmail.com> wrote: >> > I ran syncdb without a problem , then when I used the admin interface >> I >> > get the following error : >> > >> > Exception Type: DatabaseError at /admin/coordination/project/ >> > Exception Value: no such column: coordination_project.manager_id >> > >> >> syncdb only creates the table if it doesn't yet exist in your db - it >> will NOT modify an existing table. I guess you ran syncdb a first time >> before adding the manager field ? if you either have to update your >> schema manually or (better) use a schema-migration tool like South. >> >> -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/bglVN09PO6gJ. To post to this group, send email to django-users@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.
