Hi,
I don't know the exact answer to your question but what I can say is
that it is clearly dependent on your entity group hierarchy.
The key contains a concatenation of the key of all the ancestors.
I never saw any limitation on the depth of this ancestor hierarchy.
So, if you can be as deep as
hmmm thnx. it certainly did the trick.but I couldn't find the maximum
length of a key? any ideas ?
On Fri, Jan 14, 2011 at 6:42 PM, Didier Durand wrote:
> Hi,
>
> You may be interested to read to undertstand the structure of DS keys:
> http://code.google.com/appengine/articles/storage_breakdown
Hi,
You may be interested to read to undertstand the structure of DS keys:
http://code.google.com/appengine/articles/storage_breakdown.html#anc-entitiestable
And, to answer your question, you can use key.getId() (see
http://code.google.com/appengine/docs/java/javadoc/com/google/appengine/api/data
Thanks. So it is possible to use both JPA & low level API.
I tried it out , works like a charm but @ retrieval of specific object I ran
into prob you see
in my JPA, all my Entities are by long ID. How is possible for me to access
id using Key ? How may I refer keys using id & vice versa??
A lot of people were talking about moving data from Master/Slave to HR
taking to much time. I was thinking about usage of Async datastore calls to
make things several times faster.
--
You received this message because you are subscribed to the Google Groups
"Google App Engine for Java" group.
I believe the limit is 10 concurrent Async Datastore operations.
As far as transactions involving multiple entities, you could always do this
- they just have to be in the same entity group.
--
Ikai Lan
Developer Programs Engineer, Google App Engine
Blogger: http://googleappengine.blogspot.com
Re
Thanks for updated Docs. AsyncDatastoreService is really nice thing to have.
One question: how many concurent async operations are possible? Is there any
limit?
--
You received this message because you are subscribed to the Google Groups
"Google App Engine for Java" group.
To post to this grou
Hi Ikai,
As for what I have come across so far, Low level Api is useful for
performing a transaction over multiple entities. However is it possible to
use low level API as well as JPA or JDO ? The idea is to use low level api
whenever a need arises to perform a transaction over multiple enti
