And you and your users are happy with this, Tom?
I've been thinking more about entity groups, since they make this consistency
mess go away. In fact, while Entity Groups are not a great solution for all my
data, they do seem to fit for most of my models. Meetings can be parented by
Boards,
But with what countdown?
Is there an upper bound on eventually in eventually consistent? How do you
know that it's safe to do a query?
Can some people who have been using HR for a while weigh in on the longest
delay they've ever seen to consistency to be achieved?
On Sep 6, 2011, at 1:13 PM,
Hey i asked this on IRC,
It seems to be Couple of Seconds (Re-index lag)
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine/-/96weLn8jjEcJ.
To post to
How do I do a consistent get with a query? I thought that there was no way to
do a query that was guaranteed to get the lastest. Did I miss something in the
docs?
The code that builds the HTML fragment I'm caching uses a couple queries like
this:
def getBoards(self):
tid = self.id()
Yeah, that'll work, too. Unless there are two changes to the list of boards at
about the same time. Then it will give a bizarre result.
The general idea of augmenting queries with extra results that you suspect it
might not get seems to come up a lot as a solution to the eventual
consistency
My monkeypatching solution (see my recent post in the -python group), which
Guido says I shouldn't use, but which is just so darned pretty I can't help it,
has gotten me through the first challenge of switching to HR, which is dealing
with google search results containing keys into my old app's
Hi Joshua,
Can you not do a consistent get for the data when you have a cache miss, to
ensure you're fetching the latest copy, and cache that?
Looking at how NDB does its caching may be instructive here.
-Nick Johnson
On Mon, Sep 5, 2011 at 1:16 AM, Joshua Smith joshuaesm...@charter.netwrote:
