On a GAE transaction's commit, an entity is made available to other
transactions a little bit before than indexes are updated. What are
the strategies to deal with it? Did anyone solved a similar problem?

For example, I want to make a service which allows you to create nice
urls and redirect them whatever you want. Before creating a new
entity, I want to check whether the name is already occupied. With the
index update delay, it's possible to create two url with the same
name. How can I workaround this?

Thanks,
Konstantin

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine for Java" 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/google-appengine-java?hl=en.

Reply via email to