Thanks so much for your help. I think I have figured out the solution. I posted it on https://groups.google.com/forum/?hl=en#!topic/django-users/zwMWNdIqB3A.
Please take a look.
Jianbao
-- On Wed, Aug 24, 2011 at 10:13 AM, Reinout van Rees <reinout@vanrees.org> wrote:
On 24-08-11 17:57, Jianbao Tao wrote:That's in the django docs: syncdb only managed the main default database by default. You'll have to call syncdb on the second database separately.
Now './manage.py syncdb' can run through with no problems. However, it
doesn't create the database 'test.sqlite', which means the models in the
app, books, are still installed in the default database.
Often the second database is an existing one that django shouldn't touch, that's why the default is that way.
Reinout
--
Reinout van Rees http://reinout.vanrees.org/
reinout@vanrees.org http://www.nelen-schuurmans.nl/
"If you're not sure what to do, make something. -- Paul Graham"
--
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+unsubscribe@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+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
No comments:
Post a Comment