[Google-Base-API] Re: Periods in MPN field fails

i don't believe structured-queries are simple basic-matches or that products search is using structured-queries in this way in this instance. one approximation might be: bq=[mpn(text):"1942+-20"]&orderby=[x=mpn(text):if join(x)=="1942-20.5" then 0 else fail()] e.g. http://tinyurl.com/nvmh2e --~-

[Google-Base-API] Re: Periods in MPN field fails

i don't believe structured-queries are simple basic-matches or that products search is using structured-queries in this instance. one approximation might be: bq=[mpn(text):"1942+-20"]&orderby=[x=mpn(text):if join(x)=="1942-20.5" then 0 else fail()] e.g. http://tinyurl.com/nvmh2e --~--~-~

[Google-Base-API] Re: Periods in MPN field fails

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

[Google-Base-API] Re: Periods in MPN field fails

Hi.. Nice to get a qucik response from you , Can a feature string support any feature that i can provide. actually i m able to upload, publically search he item type -housing but some items are disapproved them, without knowing the reason.. all mandatory fields are mention over there, i also eli

[Google-Base-API] Re: Periods in MPN field fails

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

[Google-Base-API] Re: Periods in MPN field fails

i do not believe this is a bug at all; the results are correct within the api. although it would 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

[Google-Base-API] Re: Periods in MPN field fails

i do not believe this is a bug at all; the results are correct within the api. although it would 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

[Google-Base-API] Re: Periods in MPN field fails

i do not believe this is a bug at all; the results are correct within the api. although it would 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; the ap

[Google-Base-API] Re: Periods in MPN field fails

i do not believe this is a bug at all; the results are correct within the api. although it would 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 -- the api

[Google-Base-API] Re: Periods in MPN field fails

Replacing it with dashes did make it no longer error, but it did not pull up correct results. There are 150 sites selling that product, and only 2 showed up for [mpn:1942-20-5] ie http://www.google.com/base/feeds/snippets?bq=[mpn:1942-20-5]

[Google-Base-API] Re: Periods in MPN field fails

Google Base is not the same with Product Search. The functionality provided by these two products is different. You should not rely on the API covering all Google Product Search features (e.g. review). But the API covers functionality that's not used in Product Search. If you consider 1942-20.5 be