We are redoing old legacy J2EE/Weblogic portals in Django, so we're one of those shops that is dealing with a legacy DB (no changes to the current schema are possible).
The lack of composite key support is really starting to kill us on a few tables that we wanted to use via the Admin Inline interface. Since we can only flag 1 of the 2 columns in the PK as primary_key = True, the inline admin formset shows always 1 and only 1 row. We cannot add multiple rows. Are there any plans to add real composite key support (i.e. without just the unique_together workaround?). I understand that creating surrogate keys is an option, but not for us due to having to deal with a legacy Oracle DB. Any recommendations would be greatly appreciated. Jacek -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
