On 22 November 2013 12:35, Rasjid Wilcox <[email protected]> wrote:
> https://code.djangoproject.com/ticket/373 - Multi-part keys are still > not supported. (The ticket was opened 8 years ago.) That is a > deal-breaker for me in the work that I do. > Very true. For some applications you can work around this by creating a unique index on the multiple values and keep the primary key as a single integer. Won't help if you need to need to support existing or legacy databases however. Seems this is one feature request that is deemed too hard, breaks too much existing code, and/or not enough interest to fix. There are a number of these irritations with Django that are considered "very hard" to fix, as mentioned at Django miniconf at PyCon AU 2013. Developer's don't want to rush in with quick fixes that are later determined to be just as broken as the original code. Or break compatibility with existing applications unnecessarily. -- Brian May <[email protected]>
_______________________________________________ melbourne-pug mailing list [email protected] https://mail.python.org/mailman/listinfo/melbourne-pug
