I'm pretty sure the "your datastore is empty" message on the admin data viewer pages doesn't mean that his query, in his application code, returned no results.
While I don't disagree with you that the data is still in there I'm pretty what you just described is documented in the behavior of indexes in the data-store pretty thoroughly. If you don't index a property (or don't store it) you can not sort or search for it. As an example of your data is there, but completely invisible, try changing your app-id in your appengine-web.xml and looking at the admin page data viewer after a restart. On Thu, Feb 25, 2010 at 12:14 AM, Valters Vingolds <valt...@gmail.com> wrote: > I suspect the data is still there, but somehow not visible to your > queries. > For example, following happened in my case: I had a query that > retrieves my (root) entities, but they are ordered by sequence_id . In > 1.3.0., this query worked fine even if sequence_id is un-initialized > (is null). With 1.3.1., somehow entities with null sequence_id do not > show up in query results - and in development I had neglected to set > this field at all. So, getting empty results back: and this may lead > you to think that data has been lost. > > Though I found out that if I remove "order by" from the query, all > results show up - the data is still there. > > Now, from correctness standpoint, excluding "null" entities from > "order by" query is ok - as you can't compare against null (per SQL > rules) - so such rows may be dropped. Anyway, what I did, I wrote a > small migration script to load all my entities, initialize sequence_id > = 0 and save them. And it's now working fine with 1.3.1. > > On Feb 17, 9:06 pm, mcrady <mcr...@gmail.com> wrote: >> Same here. If I switch back to 1.3.0 the local data is still there. >> >> Any workarounds to get to 1.3.1 with the local data? >> >> On Feb 13, 10:45 am, Brian <bwa...@gmail.com> wrote: >> >> > My remote datastore kept the data, mylocalone was wiped. Pretty easy >> > to make a script to load a DB with test data, not really a good idea >> > to rely on yourlocaldatastore... >> >> > On Feb 12, 6:32 pm, mably <fm2...@mably.com> wrote: >> >> > > Same thing happened to me. >> >> > > Got an emptylocaldatastore after updating to 1.3.1. >> >> > > Hopefully I didn't have much data in it. But it might not be the case >> > > for everybody. >> >> > > On 12 fév, 09:35, Al Murauski <a.murau...@gmail.com> wrote: >> >> > > > The Development Console tells "The datastore is empty" after updating >> > > > to 1.3.1. >> >> > > > Any ideas why? I need mylocaldata back. >> >> > > > The local_db file is not emoty and contain sthe data it contained >> > > > before 1.3.1 migration. > > -- > 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 google-appengine-j...@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. > > -- 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 google-appengine-j...@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.
