Currently the Django ORM cannot handle composite keys. I am currently in the middle of migrating a legacy application to the django framework and have come across this limitation a couple of times. Our way around was to give up completely on the django ORM and switch over to the SqlAlchemy package(using Elixir for ActiveRecord like representation). Yes, we lost the "nice" admin tool, but gained a much more flexible data model. The current version of the django ORM, even considering in queryset-refactor, is tied to the admin and therefore has limitations when it comes to primary keys. Not that it's bad, it just doesn't work very well in certain circumstances.
Matt On Apr 16, 9:08 am, "Hernan Olivera" <[EMAIL PROTECTED]> wrote: > > If the question is "can it handle business logic rather than just > > be a system for writing blog software and news sites?" then most > > certainly. Several of the Django sites I've authored (they're > > internal rather than public-facing) for my company which are far > > more process-oriented in terms of business-rules. They include > > dynamic reporting, data-entry, business-rule enforcement, and > > process-flow. > > Have you written from scratch? How did you handle the composite > primary key limitation on database design? I'm trying to migrate an > entire corporate system to Django, and wandering for this stuff... > 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?hl=en -~----------~----~----~----~------~----~------~--~---
