On Tue, Dec 16, 2008 at 1:03 PM, Jacob Kaplan-Moss <jacob.kaplanm...@gmail.com> wrote: > This seems like a good idea to me, and an easy one to implement; I'm > all for it. Are there any backwards-compatibility concerns here? It > doesn't look like it -- we're just talking about adding a new hook to > SubFieldBase, right?
My only concern with this proposal so far is that I fear it'll fall short of what many people will really be looking to do here. Every time I've done this dance, I ended up something a bit more complicated, because I also needed to delay the processing of the db value until it's actually used. Basically, the same idea behind implicit ForeignKey lookups and lazy geometries in GIS. While I do realize that there are use cases where you'd want the processing to take place up front, when first loaded from the database, it seems like a slippery slope, since there are also many cases where you'd want to delay that processing. Since David's proposal doesn't address delayed processing, we'd have to make sure to manage expectations so people don't cry foul when it still doesn't do what they're looking for. I've been all for expanding how data conversion in fields is handled, and I think SubfieldBase is a great first step for common cases. I just wonder how many of the less-common cases we plan to address before we start getting into support code that's bigger and harder to maintain than custom solutions. I'm fine with the line being pushed back somewhere so we can get more support in core, but I do want to make sure a line gets drawn somewhere. Given that I've had a few encounters with this type of thing before, I'll gladly help out where I can, but I'd also want to make sure Malcolm weighs in, since I think he was intentionally conservative in determining just how much SubfieldBase was responsible for. -Gul --~--~---------~--~----~------------~-------~--~----~ 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 django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
