Michael Bayer wrote:
> I'll give you the private way to do it if you'd like to play with
> it
Cool. This will be helpful to play with for now...
> since the query already can do this, it seems harmless enough to
> create a load_only() MapperOption. However, it seems in a way to
> be fundamentally different than defer(). With defer you can say
> defer('foo.bar.data') to defer the loading of some column multiple
> levels along the relation() chain. It makes less sense with a
> load_only() option, unless we said something like load_only([x,
> y, z], path="foo.bar") which seems entirely weird (or maybe not).
> So load_only() might be made to just apply to the "mapper zero"
> position in the Query to start with (im sure that's all you or
> most people would need it for anyway).
Makes good sense to me, as it would cover my primary use case. I
would be curious to see if this pattern could be extended somehow
to be a bit more like `defer` but they are in a way inherently
different.
Thanks, let me know what you decide.
--
Jonathan LaCour
http://cleverdevil.org
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"sqlalchemy" 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/sqlalchemy?hl=en
-~----------~----~----~----~------~----~------~--~---
