On Jan 20, 3:15 pm, sago <idmilling...@googlemail.com> wrote: > I've had one very long and complex issue with a major client over > legacy databases with Composite Primary Keys (and other composite keys > more generally), an issue which has also come up in other contexts. > One of my smaller clients switched to a strange bastardization of > Django and SQLAlchemy because this was an issue. I understand the > history of #373 and why it is hard - just for disclosure.
Composite primary keys is a major issue over here and we also ended up with a bastard of SQLAlchemy and Django. -- Paulo -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
