Thanks, but I knew that :) I wanted to see if there's a way to avoid
doing this. ... I realize that sounds lazy, but it's really not ;)
I think this is something that the charts should be able to do on
their own, without my having to modify the underlying data table. They
should be able to detect that the x axis values are date or datetime
objects, and ultimately I should be able to suggest something like
{xTicksEvery:'day'} to get the axis to automatically add in the
missing days (or hours, or minutes, or whatever).
The problem with adding a date for my missing values is that I now am
altering the underlying data set. What may have been a sparse table
is now filled in with nulls. Any logic that was based on the number
of rows being equal to the number of observations needs to be
rewritten. Related to this, any aggregations that used *.count now
need to use a custom aggregation function that ignores null entries.
It's not the end of the world, but I do believe that the charts should
be able to do this themselves, without my having to add the missing
date values. It would make things a lot cleaner.
Looks like I'll need to put in an enhancement request.
And thanks for the suggestion, though; I do appreciate the tips you've
given me and others on here.
--
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.
