Hello all. I'm new to the Django community, but I have an itch that needs scratching and some time off to scratch it. The itch, of course, is composite primary and foreign keys in Django.
I've started to speak with David Cramer on the issue. Several months ago, he was pursuing a solution which he has documented here: http://code.djangoproject.com/wiki/MultipleColumnPrimaryKeys. David no longer believes that he was taking the right approach, so before I begin any work on this, I wanted to check the pulse of the developer community on the matter. Hopefully we can start a discussion to determine what the right approach is, and I can get to work implementing it. With a solid plan in place, perhaps others will want to join the cause too. The goal is to create a solution that will be worth introducing to the core Django distribution. So, if you have a moment, let's get things started here. It is understood that not everyone *needs* composite primary and foreign keys, but this is something that plenty of people do need, and it is in the interest of making the Django model layer more complete. -- 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.
