I understand that I will not have a delay in the case of using ancestor queries.
This is what I mean: (maybe I failed to make it clear). The problem we have is when you create a new entity (without using ancestor queries) and redirect the view to a list of the entities after creation, you may not see the new entity right away because it is eventually consistent unless you use ancestor queries. (This fact I am aware of). But what I wanted to know is if I can merge my older entities with my newer entity group when I try to get them. I would expect it to be done in 2 queries, one GET for the entity group and one GET for the older ungrouped entities. Then the results need to be merged and displayed back to the user. I just wanted to know if it would be worth my time trying to implement this. I need to know if there may be unexpected outcomes by doing this. I am currently assuming it would be fine, since the older entities will be already indexed and fast to get, and the entity group should be fast to get also because it was an ancestor query. So merge the results and display. I hope that makes sense & thanks for the reply, Mark -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/zidMD3mGoxEJ. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
