On Tue, Sep 16, Malcolm Tredinnick wrote: > Hopefully there won't be a need to introduce any second attribute here > (and it can't be called "pks" in any case, since that's the same problem > as before: by definition alone, there is only one pk on any table/model. > Calling it by a plural name is confusing). It's probably fairly natural > to just use "pk" always, since it can return either a single value or a > tuple in the appropriate circumstances. > [...]
I really like this approach! It could also replace unique_together. Cheers, Michael -- noris network AG - Deutschherrnstraße 15-19 - D-90429 Nürnberg - Tel +49-911-9352-0 - Fax +49-911-9352-100 http://www.noris.de - The IT-Outsourcing Company Vorstand: Ingo Kraupa (Vorsitzender), Joachim Astel, Hansjochen Klenk - Vorsitzender des Aufsichtsrats: Stefan Schnabel - AG Nürnberg HRB 17689 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
