>> 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...
Yes, it was written from scratch, and didn't involve any composite primary keys. There are some "unique-together" constraints in the DB, which could effectively be primary keys, but using a single ID column was easy enough. I also suspect there are some performance benefits to using non-composite-keys, though perhaps sharding is easier with composite-keys. -tim --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
