On Wed, Sep 9, 2009 at 4:58 AM, goobee <[email protected]> wrote: > > hi there > django's features for handling data from a database are great. > Unfortunately I work with a legacy database which does not quite fit > into djangos requirements: > > Class Member(models.Model) > mnum = models.ForeignKey(...., primary_key=True) > enum = models.ForeignKey(...., primary_key=True) > ..... > > --> no single id_... as PK > > > Would it be a big deal to change django to be able to handle these > database models? > if no, any hints where to find the 'switch' ;-) > > There is no switch. There is a ticket requesting this:
http://code.djangoproject.com/ticket/373 Karen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
