I have a number of legacy databases that I need to access from Django and they do not have a single field primary key. They have composite primary keys. There is no easy way to add the single field primary key because other programs create records and Django would not be the application that maintains and modifies these tables.
I asked about this on the Django Users list and Simone Federici said: sincerely, nobody take care about that feature because that's needed just for legacy db. The number of applications with on legacy db is less than 0.01% of the django applications. There are some workaround for that applications, for example use SQL Alchemy. I implemented a CompositeKey Dajngo feature for Django 1.4. It is completly working also for the Generic Keys, concatening escaped keys. There was also a draft to implement the indexes. However, Django core team is evolving the platform so quickly (good for the framework) and the library is not mantained anymore. On Dajngo 1.6 I had should rewrote it completly. In the end, now I understand why the core team don't care about the feature. Forget it. Should I consider his statements to be the final statement from the Django core developers? Thank you, Lance Ellinghaus -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/01043d62-a18e-4741-bcef-b3bc0a58543a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
