On Oct 20, 2010, at 5:54 PM, Alvaro Reinoso wrote:
Hello,
I'd like to know what the best choice is. This is what I do in my
system:
I'm using grok server and python on the server side; and javascript on
the client side. I store all the user data in a session object and
this data gets called twice, one to render the HTML on the server side
and another to send the data to the client side because the client
side is dynamic. I'm using joinedload right know but I know I can't
use operations such as, append and remove, when the user update or add
something.
there's no restriction on collection mutation when different loaders are
called. The collection has append(), remove(), extend(), __setitem__(), etc.
The timeout of the session object is one hour. I'd like to know if
it's better to use dynamic load because I guess with dynamic load you
have an open connection to the database, so it might take many
resources. The user object might contain a big collections of data.
use dynamic loaders if you want to load only particular slices of the
collection, instead of the whole thing at once, into memory. If you can afford
to have the whole collection in memory, then the usual loaders are better.
--
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this group, send email to sqlalch...@googlegroups.com.
To unsubscribe from this group, send email to
sqlalchemy+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/sqlalchemy?hl=en.
