On 10/19/06, flynnguy <[EMAIL PROTECTED]> wrote: > > In searching I found Ticket #373 which seems to discuss the issue but > doesn't offer a workaround or anything. I'm trying to think of how I > can make this work. I guess I could just write my own sql but I'd like > the ability to use the admin console. Does anyone have any suggestions?
Django doesn't currently have support for multiple primary keys, and as far as I know, nobody is really looking at the problem. However, as suggested in the ticket, you can work around the problem by hand writing the schema yourself (or, in your case, inheriting some schema from elsewhere), then writing a Django model that replicates everything in your schema _except_ the mutliple primary key, and use 'unique_together' as a constraint to produce behaviour similar to a multiple primary key. This approach isn't perfect, but it should get some of the admin interface working, and should allow most queries to operate without resorting to custom SQL all the time. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
