So are you proposing that the Javascript standard be changed? Or something else?
The options I see are: 1 - Change the Javascript standard 2 - You write code to offset your db query to fit the Javascript standard 3 - The GVIZ team adds a method like "monthBase()" which lets you specify whether you are using a 1 or 0 based month. This involves coding that option and automatically modifying any date or datetime objects that you have. Option 1 isn't likely to happen - if you want that, this is the wrong group :) Option 2 is the current status. Option 3 involves the Google team writing Option 2 as well as coding the option mechanism. Option 3 also adds extra weight to the google vis library, which gets distributed to each client when it's run. That's a lot of extra bits being thrown around the Internet that aren't always needed. Additionally, it means you cannot pass those objects to other Javascript libraries. It seems like Option 2 is the best one. You'd modify the date near the source, so that code for modifying it doesn't have to be distributed to everyone. And it retains compatibility with other Javascript libraries. I do recognize your annoyance with the situation! :) But once the issue was identified, I handled this one time in my data extraction layer, and haven't had to worry about it since. Took me less time to do that than write this post ;) -- You received this message because you are subscribed to the Google Groups "Google Visualization 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-visualization-api?hl=en.
