Thanks guys - that helps a lot. Cheers,
Colin
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to
Oh, and I forgot to mention, each call to allocate_ids is an RPC call
(slow), and can't be used inside a transaction (at least I had trouble with
that when I tried).
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group,
Thanks for the info Calvin.
I'm not too worried about the call being RPC slow, and I won't need to use
it inside a transaction :)
Looking at discussions
elsewherehttps://groups.google.com/d/msg/google-appengine-python/_AVE7D4P8tY/agOmNAOPSdYJ,
it would seem they should be reliably sequential
Yeah, the dev server appears to cheat and only has a single id allocator for
all types.
Also, it is fine to call allocate_ids for a kind that doesn't exist,
otherwise you couldn't allocate an id for the first model you were going to
store..
Below is a test I just ran over the remote_api. The
On Sat, Jan 29, 2011 at 5:11 PM, Colin Hawkett hawk...@gmail.com wrote:
Thanks for the info Calvin.
I'm not too worried about the call being RPC slow, and I won't need to use
it inside a transaction :)
Looking at discussions
