On Tue, Dec 16, 2008 at 2:02 PM, David Cramer <dcra...@gmail.com> wrote: > Could we just use a lazy proxy for the value value? When it's executed, it > could then just call the get_value_from_db method (or whatever).
I expect that the lazy approach is what most people would really want, so I'd be fine with that. I didn't want to assume that's what you wanted, though, since you may have a good reason to want your data processed immediately upon loading, rather than on first use. Personally, I'd recommend that if we go this route, we go with full-on lazy loading. I'd recommend against updating ForeignKey and GIS code to use it, though, since they currently use two different approaches. Merging them would likely introduce some interesting gotchas for people who are relying on the specific technique used behind the scenes. I'm still reserving a bit of judgment, though, until we get some code together that proves useful in a good half-dozen different situations (at least). The only thing worse than not implementing as much of the feature as people want would be to implement all of it but make them reimplement it because it's not flexible enough to suit their needs. -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 -~----------~----~----~----~------~----~------~--~---
