I suspect you had already done a syncdb before creating that field. If yes, the database would not create it just like that. When I had similar problem, here's what I did. I removed the database file from my project root and then ran a syncdb again. It worked. There's a price to pay however, you would lose everything in the database and you have to repopulate again. HTH Sent from my BlackBerry wireless device from MTN
-----Original Message----- From: electrocoder <electroco...@gmail.com> Sender: django-users@googlegroups.com Date: Mon, 28 Feb 2011 11:44:34 To: Django users<django-users@googlegroups.com> Reply-To: django-users@googlegroups.com Subject: DatabaseError at / no such table: cms_page How do "DatabaseError at / no such table: cms_page" -- 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 django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en. -- 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 django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
