Le Friday 08 March 2013 18:50:09, Laurence Rowe a écrit :
It would be great if there was a way to advise ZODB in advance that
certain objects would be required so it could fetch multiple object
states in a single request to the storage server.
+1
I can see this used to process a large tree,
On Fri, Mar 8, 2013 at 9:54 PM, Siddhartha Kasivajhula
countvajh...@gmail.com wrote:
Hi there,
I've been discussing this issue with Laurence Rowe on the pylons-dev mailing
list, and he suggested bringing it up here.
I'm writing a MongoDB data manager for the python transaction package:
On Sat, Mar 9, 2013 at 5:50 AM, Vincent Pelletier plr.vinc...@gmail.com wrote:
Le Friday 08 March 2013 18:50:09, Laurence Rowe a écrit :
It would be great if there was a way to advise ZODB in advance that
certain objects would be required so it could fetch multiple object
states in a single
On Sat, Mar 9, 2013 at 9:02 AM, Jim Fulton j...@zope.com wrote:
...
I think a simple method on a storage that gives a hint that a set of
object ids will be loaded is enough. A network storage could then
issue a pipelined request for those oids. The application can then
proceed as usual. I
Nope. This is a bug.
Really, ``begin` and ``abort`` are equivalent. It might be better if
there wasn't a ``begin`` method, as it's missleading. One should be an
alias for the other. I'd be for deprecating ``begin``. The call to
``_new_transaction`` should be moved to the point in ``get``
