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
-~----------~----~----~----~------~----~------~--~---

Reply via email to