I don't want to do anything complex, just a basic match. MPN is equal to the exact string 1942-20.5. There appears to be no way to do this because it has a period. Since there is no way to slash that period and tell the API not to try to do something fancy with it, an error occurs. How is that not a bug? If there was a published workaround than the bug would be in my own code. Since no workaround exists it is definitely an API bug, it can't handle periods properly and there is no way to tell it a period is just a period.
--Robert On Sat, Aug 1, 2009 at 3:01 PM, Celebird <[email protected]> wrote: > > i do not believe this is a bug at all; > the results are correct within the api. > > although it might be nice to have exact regular-expression matching -- > both structured and full-text api queries are more geared toward and > defined around the concept of relevancy and returning relevant results > but the api does not support the concept of exact pattern-matching. > > the google-products feature has augmented this possible shortcoming; > all that can be done with the api is to approximate google-products. > > the approximation is most probably as alex suggested -- > search by a relevant term and narrow results internally; > for example, use a standardized regular-expression engine. > > the period and other symbols do not have > abilities of well-known pattern-matching > or formal posix regular-expressions syntax > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
