Something has definitely changed within the past few days in the
processing of structured queries through the Google Spreadsheets Data
API. I am also encountering the "invalid token" exception on queries
that have worked for months. In my case the offending character is
"#". As I have always done, the text is enclosed in quotes. When
encountering this error yesterday (and again today), I tried both URL
and HTML encoding to see if that would resolve this new error.
Neither was successful. I am looking for guidance as to the nature of
the change in structured query processing and how we are supposed to
now handle non-alpha characters in queries.
On Dec 29, 8:43 am, Erwin Quinto <erwin.qui...@gmail.com> wrote:
> Hi I'm using Google Spreadsheets Data API for my current project. We
> stored employee records on the a google spreadsheet. We have a
> requirement toqueryall records with the given email address. Here's
> my sample code:
>
> RecordQueryquery= new RecordQuery(recordsFeedUrl);
> query.setSpreadsheetQuery("email=some...@there.org");
> System.out.println(query.getUrl().toString());
> RecordFeed feed = service.query(query, RecordFeed.class);
>
> When I try to run it an "Parse error: Invalidtokenencountered" error
> is thrown. Doing some experiments I found out that the "@" character
> is the one causing the trouble. Would anyone here know how to go about
> this? Did anybody already encountered similar problem?
--
You received this message because you are subscribed to the Google Groups
"Google Docs Data APIs" group.
To post to this group, send email to google-docs-data-a...@googlegroups.com.
To unsubscribe from this group, send email to
google-docs-data-apis+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/Google-Docs-Data-APIs?hl=en.
