David Cramer wrote:
> I'd like to present my concept for partial models, which would be an
> attempt to replace the use of .values() returning a dictionary
> (although .values() still has uses if you dont actually want an
> instance). Keep in mind, the way I'm presenting this would keep #17
> working :)
> 
> values, values_tuple, and partial models, in my opinion, should all be
> replaced with one method call (what if theres a values_list or
> values_set, seems ugly). This would become a new values method:
> 
> values(results=[object|tuple|dict]) or something similar
> 
> Upon returning the object, you would get proxies, which held a model
> instance in it.

However, one of the benefits of values() returning a dict is that you 
avoid the more expensive model instance creation when you don't need it. 
  So I lean more towards something like #5420 rather than changing what 
values() returns.

And, if you would rather be explicit in the positive tone, then maybe a 
show() method to complement the hide() would satisfy you.

Gary

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to