multi-column field support (#5929)

2 views
Skip to first unread message

Justin Fagnani

unread,
Sep 9, 2008, 5:33:40 PM9/9/08
to django-d...@googlegroups.com
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.

Hope everyone's recovering and relaxing well post-1.0/djangocon.

-Justin

[1] http://groups.google.com/group/django-developers/msg/4f75b4d9f569f8a9

Malcolm Tredinnick

unread,
Sep 9, 2008, 7:08:23 PM9/9/08
to django-d...@googlegroups.com

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


Justin Fagnani

unread,
Sep 9, 2008, 9:10:59 PM9/9/08
to django-d...@googlegroups.com
On Tue, Sep 9, 2008 at 4:08 PM, Malcolm Tredinnick
<mal...@pointy-stick.com> wrote:
> I've got most of it done locally, but I need to port it forwards to
> match recent changes on trunk
...

> if you haven't seen anything in a week, ping me again.

Thanks, that's great to hear.

-Justin

David Cramer

unread,
Sep 10, 2008, 4:33:39 AM9/10/08
to Django developers
Ya, depending on how support is planned I may be able to remove some
of the composite pk hacks.

FYI the last patch I threw up didn't work in all areas, but I do have
it running on our staging environment now without issues (so far). The
code is only very slightly changed though.

On Sep 9, 8:10 pm, "Justin Fagnani" <justin.fagn...@gmail.com> wrote:
> On Tue, Sep 9, 2008 at 4:08 PM, Malcolm Tredinnick
>
Reply all
Reply to author
Forward
0 new messages