Comments on: FuzzyDates, or: One Django Model Field, multiple database columns

By: Bohdan

Bohdan — Wed, 20 Jul 2011 15:45:19 +0000

Thanks! Have you tried using it with dmigrations, django_evolution?

By: Ivan Virabyan

Ivan Virabyan — Fri, 25 Feb 2011 12:11:23 +0000

Thank you so much, I was going to implement the exactly same thing, but you saved my time.

By: admin

admin — Wed, 09 Jan 2008 17:20:35 +0000

Thanks for your comment, Malcolm.

I haven’t looked at generic relations at all so far, which is something I know regret. I wasn’t aware that they need to deal with the same issue. I’ll check them out.

By: Malcolm Tredinnick

Malcolm Tredinnick — Tue, 08 Jan 2008 23:33:46 +0000

Well done. This is a very logical approach. The SubfieldBase metaclass is just a helper class for the common case; it’s not required to use it and people *should* just write their own __get__ and __set__ methods when they need to, as you’ve done.

Making this work in the fully general case (where lookups work) is actually pretty fiddly. I’ve been working on a design for a couple of weeks now without having anything brilliant pop out (although it seems to be getting closer). So it’s work in progress. We need it for reverse-lookups with generic relations for example — which map two database columns to one model attribute.