[google-appengine] Re: GQL query failed to return a qualifying entity
In the beginning of Appengine some objects got lost in the index. The solution was get the object by key and put() it again. This solved it for some people who where missing objects with a query that has a filter. If you don't know the key of the object, page over all keys of that object type and re-put() them all. 2009/8/6 Jaap Taal j...@q42.nl: Hi phtq, I've only had this problem once, and after deleting that record it never occured again... The only reason I mentioned it, is because you started this thread! Jaap On Wed, Aug 5, 2009 at 11:28 PM, phtq pher...@typequick.com.au wrote: Hello Jaap, Sounds like this problem is not all that rare, although we have never hit it before in over a year of development on the app engine. I can't relate the problem to anything we have done recently. I don't think we have introduced any new indexes for a while for example. I take it Google have not come up with any explanation in your case so far either? On Aug 5, 11:18 pm, Jaap Taal j...@q42.nl wrote: Same here, just good old ASCII chars in that record. On Wed, Aug 5, 2009 at 12:55 AM, phtq pher...@typequick.com.au wrote: The fact that the record can be retrieved with any 2 of the 3 filters indicates that there are no hidden characters. On Aug 5, 8:41 am, Wooble geoffsp...@gmail.com wrote: Are you sure there isn't a space or other non-printable character in your data in the datastore? It's certainly possible your index is corrupt, but I'd check for more likely causes first. On Aug 4, 12:01 am, phtq pher...@typequick.com.au wrote: In our application (kbdlessons version 1-01) we have just had a case where a query in our application failed to return a record which definitely exists. We were able to reproduce this problem using the Dataviewer page off the app engine dashboard. We put in this query using the Dataviewer: SELECT * FROM StudentSubscriptions where StudentKey = 'REBECCA' and ProductKey = 'Typequick Professional' and AccountKey = 'SIVF' and got no results. However, if we use just 2 out of the 3 tests (any 2!) the record we want appears amongst the results. Also, other valid values for StudentKey when used in this 3 part query do return a record in the Dataviewer page, just not this particular set of 3 values. We had to build a new record (under another name) to get the student going, but have left the troubled record in the database so you can look at it. Please let me know how to avoid this rather worrying problem. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: GQL query failed to return a qualifying entity
Hi phtq, I've only had this problem once, and after deleting that record it never occured again... The only reason I mentioned it, is because you started this thread! Jaap On Wed, Aug 5, 2009 at 11:28 PM, phtq pher...@typequick.com.au wrote: Hello Jaap, Sounds like this problem is not all that rare, although we have never hit it before in over a year of development on the app engine. I can't relate the problem to anything we have done recently. I don't think we have introduced any new indexes for a while for example. I take it Google have not come up with any explanation in your case so far either? On Aug 5, 11:18 pm, Jaap Taal j...@q42.nl wrote: Same here, just good old ASCII chars in that record. On Wed, Aug 5, 2009 at 12:55 AM, phtq pher...@typequick.com.au wrote: The fact that the record can be retrieved with any 2 of the 3 filters indicates that there are no hidden characters. On Aug 5, 8:41 am, Wooble geoffsp...@gmail.com wrote: Are you sure there isn't a space or other non-printable character in your data in the datastore? It's certainly possible your index is corrupt, but I'd check for more likely causes first. On Aug 4, 12:01 am, phtq pher...@typequick.com.au wrote: In our application (kbdlessons version 1-01) we have just had a case where a query in our application failed to return a record which definitely exists. We were able to reproduce this problem using the Dataviewer page off the app engine dashboard. We put in this query using the Dataviewer: SELECT * FROM StudentSubscriptions where StudentKey = 'REBECCA' and ProductKey = 'Typequick Professional' and AccountKey = 'SIVF' and got no results. However, if we use just 2 out of the 3 tests (any 2!) the record we want appears amongst the results. Also, other valid values for StudentKey when used in this 3 part query do return a record in the Dataviewer page, just not this particular set of 3 values. We had to build a new record (under another name) to get the student going, but have left the troubled record in the database so you can look at it. Please let me know how to avoid this rather worrying problem. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: GQL query failed to return a qualifying entity
Same here, just good old ASCII chars in that record. On Wed, Aug 5, 2009 at 12:55 AM, phtq pher...@typequick.com.au wrote: The fact that the record can be retrieved with any 2 of the 3 filters indicates that there are no hidden characters. On Aug 5, 8:41 am, Wooble geoffsp...@gmail.com wrote: Are you sure there isn't a space or other non-printable character in your data in the datastore? It's certainly possible your index is corrupt, but I'd check for more likely causes first. On Aug 4, 12:01 am, phtq pher...@typequick.com.au wrote: In our application (kbdlessons version 1-01) we have just had a case where a query in our application failed to return a record which definitely exists. We were able to reproduce this problem using the Dataviewer page off the app engine dashboard. We put in this query using the Dataviewer: SELECT * FROM StudentSubscriptions where StudentKey = 'REBECCA' and ProductKey = 'Typequick Professional' and AccountKey = 'SIVF' and got no results. However, if we use just 2 out of the 3 tests (any 2!) the record we want appears amongst the results. Also, other valid values for StudentKey when used in this 3 part query do return a record in the Dataviewer page, just not this particular set of 3 values. We had to build a new record (under another name) to get the student going, but have left the troubled record in the database so you can look at it. Please let me know how to avoid this rather worrying problem. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: GQL query failed to return a qualifying entity
Hello Jaap, Sounds like this problem is not all that rare, although we have never hit it before in over a year of development on the app engine. I can't relate the problem to anything we have done recently. I don't think we have introduced any new indexes for a while for example. I take it Google have not come up with any explanation in your case so far either? On Aug 5, 11:18 pm, Jaap Taal j...@q42.nl wrote: Same here, just good old ASCII chars in that record. On Wed, Aug 5, 2009 at 12:55 AM, phtq pher...@typequick.com.au wrote: The fact that the record can be retrieved with any 2 of the 3 filters indicates that there are no hidden characters. On Aug 5, 8:41 am, Wooble geoffsp...@gmail.com wrote: Are you sure there isn't a space or other non-printable character in your data in the datastore? It's certainly possible your index is corrupt, but I'd check for more likely causes first. On Aug 4, 12:01 am, phtq pher...@typequick.com.au wrote: In our application (kbdlessons version 1-01) we have just had a case where a query in our application failed to return a record which definitely exists. We were able to reproduce this problem using the Dataviewer page off the app engine dashboard. We put in this query using the Dataviewer: SELECT * FROM StudentSubscriptions where StudentKey = 'REBECCA' and ProductKey = 'Typequick Professional' and AccountKey = 'SIVF' and got no results. However, if we use just 2 out of the 3 tests (any 2!) the record we want appears amongst the results. Also, other valid values for StudentKey when used in this 3 part query do return a record in the Dataviewer page, just not this particular set of 3 values. We had to build a new record (under another name) to get the student going, but have left the troubled record in the database so you can look at it. Please let me know how to avoid this rather worrying problem. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: GQL query failed to return a qualifying entity
I've experienced a similar problem running on the SDK.aplying two filter()s result in 0 records found. Aplying either one of the filter()s and comparing the resultsets found a record that matches both filter()s. Jaap Taal [ Q42 BV | tel 070 44523 42 | direct 070 44523 65 | http://q42.nl | Waldorpstraat 17F, Den Haag | KvK 30164662 ] On Tue, Aug 4, 2009 at 6:01 AM, phtq pher...@typequick.com.au wrote: In our application (kbdlessons version 1-01) we have just had a case where a query in our application failed to return a record which definitely exists. We were able to reproduce this problem using the Dataviewer page off the app engine dashboard. We put in this query using the Dataviewer: SELECT * FROM StudentSubscriptions where StudentKey = 'REBECCA' and ProductKey = 'Typequick Professional' and AccountKey = 'SIVF' and got no results. However, if we use just 2 out of the 3 tests (any 2!) the record we want appears amongst the results. Also, other valid values for StudentKey when used in this 3 part query do return a record in the Dataviewer page, just not this particular set of 3 values. We had to build a new record (under another name) to get the student going, but have left the troubled record in the database so you can look at it. Please let me know how to avoid this rather worrying problem. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: GQL query failed to return a qualifying entity
Are you sure there isn't a space or other non-printable character in your data in the datastore? It's certainly possible your index is corrupt, but I'd check for more likely causes first. On Aug 4, 12:01 am, phtq pher...@typequick.com.au wrote: In our application (kbdlessons version 1-01) we have just had a case where a query in our application failed to return a record which definitely exists. We were able to reproduce this problem using the Dataviewer page off the app engine dashboard. We put in this query using the Dataviewer: SELECT * FROM StudentSubscriptions where StudentKey = 'REBECCA' and ProductKey = 'Typequick Professional' and AccountKey = 'SIVF' and got no results. However, if we use just 2 out of the 3 tests (any 2!) the record we want appears amongst the results. Also, other valid values for StudentKey when used in this 3 part query do return a record in the Dataviewer page, just not this particular set of 3 values. We had to build a new record (under another name) to get the student going, but have left the troubled record in the database so you can look at it. Please let me know how to avoid this rather worrying problem. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: GQL query failed to return a qualifying entity
The fact that the record can be retrieved with any 2 of the 3 filters indicates that there are no hidden characters. On Aug 5, 8:41 am, Wooble geoffsp...@gmail.com wrote: Are you sure there isn't a space or other non-printable character in your data in the datastore? It's certainly possible your index is corrupt, but I'd check for more likely causes first. On Aug 4, 12:01 am, phtq pher...@typequick.com.au wrote: In our application (kbdlessons version 1-01) we have just had a case where a query in our application failed to return a record which definitely exists. We were able to reproduce this problem using the Dataviewer page off the app engine dashboard. We put in this query using the Dataviewer: SELECT * FROM StudentSubscriptions where StudentKey = 'REBECCA' and ProductKey = 'Typequick Professional' and AccountKey = 'SIVF' and got no results. However, if we use just 2 out of the 3 tests (any 2!) the record we want appears amongst the results. Also, other valid values for StudentKey when used in this 3 part query do return a record in the Dataviewer page, just not this particular set of 3 values. We had to build a new record (under another name) to get the student going, but have left the troubled record in the database so you can look at it. Please let me know how to avoid this rather worrying problem. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
