Well GenericRelation's or whatever are an attempt to provide some composite space, but we need an expandable space, not something tied to content type's. We need to say mykey = CompositeField(field, field, field) or something.
No one wanted to discuss it at DjangoCon, so no. On Thu, Oct 30, 2008 at 3:57 PM, Joey Wilhelm <[EMAIL PROTECTED]> wrote: > That would be great. The project I am working on now won't be doing > anything too terribly complex just yet; I mainly need the admin support to > make my life a little easier. > > As to the API, I saw several proposals earlier along on this thread, but > obviously nothing solid. Did anything ever come from DjangoCon on this > topic? What issues still need to be addressed in this design? > > On Thu, Oct 30, 2008 at 13:46, David Cramer <[EMAIL PROTECTED]> wrote: > >> It allows you to use them, automatically creates them, and has some of the >> admin handling done. However, there's still no API design around >> multi-column fields (no one seems to want to talk about it) so I'm pretty >> much stopped working on it. >> >> e.g. You can't say field1 = this, field2 = that, and then say compositekey >> = field1,field2 you instead are forced to do key1=blah, key2=blah in all >> your lookups, and no easy foreignkey properties. >> >> I'm running this on production environments, so it works fine, but I can >> up SVN and fix any conflicts and post a patch again. >> >> -- >> David Cramer >> Director of Technology >> iBegin >> http://www.ibegin.com/ >> >> >> > > > > -- David Cramer Director of Technology iBegin http://www.ibegin.com/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
