Checked this out and it does appears to be a bug to me. The workaround appears to be the best solution but not a perfect one as you say.
Try submitting it here: http://code.google.com/p/gdata-issues/issues/list Please post a link to it here so other users can track it. On May 8, 6:51 pm, pmdpmd <[email protected]> wrote: > Hmm... It is looking more like a bug. I tried a few more queries: > > Price==11.99 does not work (as above). > Price==12.00 works ok > Price==12.99 does not work > Price==13.00 works ok > Price==13.99 does not work > Price==14.00 works ok > > It seems to be to do with whole numbers. > > My work round at the moment is to put in both limits e.g. [Price>11.98] > [Price<12.00] when I need products at 11.99 - this generally works but > I am getting occasional anomalies - e.g. products at 4.99 returned in > my result set for that query. Has anyone experienced this? Do you > think it is as a result of my workround, or is this what others are > experiencing - i.e. some low level of incorrect results returned? > > Thanks, > Paul. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Base Data API" 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-Base-data-API?hl=en -~----------~----~----~----~------~----~------~--~---
