mattdrayer/api-time-series-fix: Use backticks instead of quotes

@martynjames -- took a bit of time to get to the bottom of things, but the issue with the time series data stemmed from a MySQL syntax issue -- changing one of the query clauses to use backticks instead of quotes resolved the issue.  Apparently the quotes are valid for sqlite, which explains why the unit tests did not catch the problem.  Not sure if you're able to repro on your end, but take a look and let me know either way -- we should at least be able to see how it looks in the QA environment once merged.

@ziafazal, FYI on the syntax change
pretty sure we want the backtick, although I will give the single quote a
try locally to see how that goes

On Wed, Oct 22, 2014 at 4:49 PM, Martyn James <notifications@github.com>
wrote:

> In lms/djangoapps/api_manager/utils.py:
>
> > @@ -152,7 +152,7 @@ def get_time_series_data(queryset, start, end, interval='days', date_field='crea
> >      _, end = get_interval_bounds(end, interval.rstrip('s'))
> >
> >      if date_field_model:
> > -        date_field = '"{}"."{}"'.format(date_field_model._meta.db_table, date_field)
> > +        date_field = '`{}`.`{}`'.format(date_field_model._meta.db_table, date_field)
>
> Are we sure we want ` - or do we want ' ?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/edx-solutions/edx-platform/pull/281/files#r19243143>.
>



-- 
Matthew Drayer
Solutions Architect
edX | MIT
mattdrayer@edx.org