Monday October 2, 2006
Seemant,
I am new to django, but from my computer science and database background
understand your question in regards to how databases work. The table
'people_role' would be a "linking table" for correct database
relationship of performing a many-to-many operation. It basically
consists of a foreign key for people and a foreign key for role. From
the error message you provided, it sounds like django is accurately
recognizing it as a many-to-many operation by looking for the table
'people_role'.
I suggest creating a table like (psudo-code):
people_role {
people_id
role_id
}
(Once again, I am new to django so a more experienced django developer
please confirm or counter what I am suggesting.) For syncdb to work,
you might want to try creating an object in model.py for 'people_role'.
It is good that django tries to look for a linking table regarding a
many-to-many relationship, but is django also supposed to create a
"linking table" or is that left to the developer?
Best Regards,
Ben DruShell
----------------------------------------------------------
On Mon, 2006-10-02 at 17:54 -0400, Seemant Kulleen wrote:
> Dear All,
>
> I've attached two files: people/models.py and services/models.py. I
> have two many-to-many relationships defined: one is between people and
> roles (each person can fill many roles, and each role can be filled by
> many people); and one is between each activity in the service (banner
> bearer, crucifer, and so on) and people (each activity can be performed
> by many people in a specific role and each person can perform many
> activities). Chris Long and tomaw helped me come up with appropriate
> "limit_choices_to" constructs in the services/models.py to restrict each
> activity to specific roles -- so that in the admin etc, only specific
> people are presented as choices for each activity. Now, when I run
> python manage.py syncdb (with sqlite3 and postgresql both), I get the
> following error:
>
>
> Error: Couldn't install apps, because there were errors in one or more
> models:
> 3crowns.services: no such table: people_role
>
>
> However, if I remove the limit_choices_to and then syncdb, it succeeds.
> If I then re-add the limit_choices_to constructs and run: python
> manage.py reset services I get no errors, and in fact, the admin view
> shows exactly what I expect/hope it will show.
>
> This is either a bug with me or a bug with django, and when I think
> about it, I reckon it's a bug with me, so I appeal for your help :)
>
> Thanks!
>
>
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
