Re: problem with models and foreign keys

2008-07-01 Thread Malcolm Tredinnick
On Tue, 2008-07-01 at 00:09 -0700, KevinTran wrote: > So that means that the tables are correct right? Yes, they're fine. It's just a subtle difference between what "manage.py sql ..." and "manage.py sqlall ..." prints out. When you run "manage.py syncdb", it will use the "sqlall" equivalent.

Re: problem with models and foreign keys

2008-07-01 Thread KevinTran
So that means that the tables are correct right? Is there a way to control the order of the table creation? On Jul 1, 12:05 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > Because the link table is created after the Bookmarks one that would > be a reference to a non-existant table, if you

Re: problem with models and foreign keys

2008-07-01 Thread [EMAIL PROTECTED]
Because the link table is created after the Bookmarks one that would be a reference to a non-existant table, if you use the sqlall command instead you will see that the tables are altered to add the constraint. On Jul 1, 1:57 am, KevinTran <[EMAIL PROTECTED]> wrote: > Hi I'm currently reading

problem with models and foreign keys

2008-07-01 Thread KevinTran
Hi I'm currently reading Learning Website Development with Django and I'm having a problem with models. Here is my models.py: from django.db import models from django.contrib.auth.models import User class Link(models.Model): url = models.URLField(unique=True) class