On Tue, 2008-09-09 at 14:33 -0700, Justin Fagnani wrote: > I forgot to mention this as one of my ponies at djangocon, but I'd > really love to have multi-column fields. I particularly need this for > measurement and currency fields, which I think would be awesome to > have built-in. > > So is anyone working on #5929? I see an email from Malcolm in March[1] > that mentions that he might have had some pieces of the puzzle coming > with qs-rf. At first glance it certainly doesn't appear too hard, > except that I'm not sure how much this issue interacts with #373. I > think I see where the logical changes would go and I'd be willing to > put the work in on this over the next couple of weeks.
I've got most of it done locally, but I need to port it forwards to match recent changes on trunk (it's about 400 - 500 revisions behind at the moment). I dropped in a more-or-less hack to make GenericRelations in filters work before 1.0 because I couldn't get this finished in time. That's just a temporary solution (well, it's part of the final solution, but needs a little more thinking to make it truly portable). It probably helps with the pieces David's finding hard in his latest multi-col primary key stuff, but before I go forwards with generic multicolumn stuff, I need to review David's patch and make sure we're both heading in roughly the same direction. That's probably a couple of days away at the moment, since I'm a bit loaded up right now, but if you haven't seen anything in a week, ping me again. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
