On 11/27/06, Maciej Bliziński <[EMAIL PROTECTED]> wrote: > Do you have any ideas how to solve my problem? Should the above class be > valid and should Django successfully create the tables? Or is there some > other way to map objects from two classes in 1-1 manner without creating > additional columns in their database tables?
Doing two one-to-one relations on a single model won't work, because a one-to-one field becomes the primary key of the model's database table, and Django doesn't handle multiple-column primary keys at the moment. A better solution would probably be just a pair of foreign keys, or one foreign key and one one-to-one field (if possible, make the one-to-one point to Django's User model so you can use AUTH_PROFILE_MODULE). -- "May the forces of evil become confused on the way to your house." -- George Carlin --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
