I manually reverted it to 2010 because I didn't want to cause problems with
your app by fudging with the data. It didn't revert automatically. I just
ran this GQL query:

SELECT * FROM Search_update ORDER BY last_check DESC LIMIT 10

And it displayed the data correctly.

Is there any chance you're setting a different read consistency?

http://code.google.com/appengine/docs/python/datastore/queriesandindexes.html#Setting_the_Read_Policy_and_Datastore_Call_Deadline

I understand your frustration with regards to paid support - but our pricing
structure doesn't bundle in a guarantee for a support response time. We make
every effort to address any issues in production either behind the scenes,
through proactive monitoring or to reactive reports via the different
channels we keep track of, but we simply can't scale up a direct support
option for developers who want to be able to pick up the red phone and get
someone on the line immediately when there are service issues. In terms of
addressing service degradation without additional cost to developers, based
on conversations we have had with developers, I believe that we are as good
if not much better than the industry standard for platform, managed cloud
hosting. There are companies who will always have a resource for you
available, but there's a reason any kind of baseline production spend will
be in the hundreds of dollars - minimum. We're doing our best to minimize
costs, support all developers on our platform, all while not charging
developers who don't require a response time SLA.

On Fri, Jul 9, 2010 at 2:24 PM, Daniel <[email protected]> wrote:

> When I run the query Search_update.all().order('last_check').fetch(10)
> programtically I consistently get this response:
>
> agtsb294aWktYmV0YXIVCxINU2VhcmNoX3VwZGF0ZRi62AUM 2010-07-09
> 17:57:37.894714
> agtsb294aWktYmV0YXIVCxINU2VhcmNoX3VwZGF0ZRjsm3kM 2010-07-08
> 00:27:52.385926
> agtsb294aWktYmV0YXIVCxINU2VhcmNoX3VwZGF0ZRipkjsM 2010-07-08
> 00:27:53.689982
> agtsb294aWktYmV0YXIWCxINU2VhcmNoX3VwZGF0ZRiqu7ABDA 2010-07-08
> 00:27:54.616698
> agtsb294aWktYmV0YXIVCxINU2VhcmNoX3VwZGF0ZRiTrVwM 2010-07-08
> 00:27:55.453521
> agtsb294aWktYmV0YXIVCxINU2VhcmNoX3VwZGF0ZRjksQUM 2010-07-08
> 00:27:56.437609
> agtsb294aWktYmV0YXIWCxINU2VhcmNoX3VwZGF0ZRjp_KwBDA 2010-07-08
> 00:28:02.699297
> agtsb294aWktYmV0YXIVCxINU2VhcmNoX3VwZGF0ZRiRqAUM 2010-07-08
> 00:28:04.598150
> agtsb294aWktYmV0YXIWCxINU2VhcmNoX3VwZGF0ZRjyzK8BDA 2010-07-08
> 00:28:05.595406
> agtsb294aWktYmV0YXIVCxINU2VhcmNoX3VwZGF0ZRi-2AUM 2010-07-08
> 00:28:07.950788
>
> Which places the record in question first in the query although it has
> a date later than the listed records.  You can also see that having
> just run the response that the 2011 date reverted.  It appears to
> change when you save it, but it doesn't actually change.
>
> On Jul 9, 5:14 pm, "Ikai L (Google)" <[email protected]> wrote:
> > Using this GQL query in the admin console:
> >
> > SELECT * FROM Search_update where
> > __key__=KEY('agtsb294aWktYmV0YXIVCxINU2VhcmNoX3VwZGF0ZRi62AUM')
> >
> > I was able to set the year to 2011, see the changes reflected, then set
> them
> > back to 2010 (I didn't want to cause issues with your application). How
> are
> > you reproducing your issues? Can you see if you can update the timestamp
> in
> > the datastore viewer?
> >
> >
> >
> >
> >
> > On Fri, Jul 9, 2010 at 12:24 PM, Daniel <[email protected]>
> wrote:
> > > Thanks for the fast response.  The kind is Search_update.
> >
> > > On Jul 9, 3:16 pm, "Ikai L (Google)" <[email protected]> wrote:
> > > > Hi Daniel,
> >
> > > > What is the Entity Kind?
> >
> > > > The best thing I would recommend in the future is the billing support
> > > form:
> >
> > > >
> http://code.google.com/support/bin/request.py?contact_type=AppEngineB...
> >
> > > > This is a monitored queue for issues like these, and I expect that we
> > > will
> > > > be emphasizing it more. We're not currently equipped to handle
> dedicated
> > > > support, though it is on our roadmap to offer paid support with an
> SLA
> > > for
> > > > response time.
> >
> > > > On Fri, Jul 9, 2010 at 12:10 PM, Daniel <[email protected]>
> > > wrote:
> > > > > I have a record which is frozen in the datastore and always shows
> the
> > > > > current time.  This record is blocking a major time sorted query in
> my
> > > > > application.  I've had this same problem in June (http://
> > > > > groups.google.com/group/google-appengine/browse_thread/thread/
> > > > > b0021ac81b8c24a5/dcf6c71e3e0b3083) and I had to get a tech to fix
> it.
> > > > > Please help me correct this record.  The app is looxii-beta and the
> > > > > key is agtsb294aWktYmV0YXIVCxINU2VhcmNoX3VwZGF0ZRi62AUM.
> >
> > > > > As an aside, it seems ridiculous to me that the database would not
> > > > > perform as it should.  This is a major issue, and actually blocks
> my
> > > > > application from properly performing.  I accept that AppEngine is
> in
> > > > > beta, but at least give your paying customers a contact email
> address
> > > > > so that when we have legitimate issues we don't have to post to a
> > > > > public forum and wait for a google rep to stumble upon our issue.
> >
> > > > > --
> > > > > You received this message because you are subscribed to the Google
> > > Groups
> > > > > "Google App Engine" group.
> > > > > To post to this group, send email to
> [email protected]
> > > .
> > > > > To unsubscribe from this group, send email to
> > > > > [email protected]<google-appengine%[email protected]><google-appengine%2Bunsubscrib
> [email protected]><google-appengine%2Bunsubscrib
> > > [email protected]>
> > > > > .
> > > > > For more options, visit this group at
> > > > >http://groups.google.com/group/google-appengine?hl=en.
> >
> > > > --
> > > > Ikai Lan
> > > > Developer Programs Engineer, Google App Engine
> > > > Blog:http://googleappengine.blogspot.com
> > > > Twitter:http://twitter.com/app_engine
> > > > Reddit:http://www.reddit.com/r/appengine
> >
> > > --
> > > You received this message because you are subscribed to the Google
> Groups
> > > "Google App Engine" group.
> > > To post to this group, send email to [email protected]
> .
> > > To unsubscribe from this group, send email to
> > > [email protected]<google-appengine%[email protected]><google-appengine%2Bunsubscrib
> [email protected]>
> > > .
> > > For more options, visit this group at
> > >http://groups.google.com/group/google-appengine?hl=en.
> >
> > --
> > Ikai Lan
> > Developer Programs Engineer, Google App Engine
> > Blog:http://googleappengine.blogspot.com
> > Twitter:http://twitter.com/app_engine
> > Reddit:http://www.reddit.com/r/appengine
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected]<google-appengine%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>
>


-- 
Ikai Lan
Developer Programs Engineer, Google App Engine
Blog: http://googleappengine.blogspot.com
Twitter: http://twitter.com/app_engine
Reddit: http://www.reddit.com/r/appengine

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

Reply via email to