Getting rid of RuntimeWarning: DateTimeField received a naive datetime + is there something like TimeField? about djangoql HOT 4 CLOSED

thanks, good catch about timezone! Actually, this is not just about warnings. That behavior could result in weird situations when timezone is different between a database and Django settings, so I made a fix which sets timezone explicitly for both DateField and DateTimeField. Please check v0.8.6

as for TimeField - yeah, I suppose custom field would be a reasonable way to go

from djangoql.

Thanks, that looks great, now I can just have nice "2017-01-02" in my test (and DjangoQL will correctly set the timezone).

However, one test in my project that was passing before is now failing with AssertionError: 3 != 0:

http_status, response_json = self._get(
    '/users/user_1/meals/',
    {'filter': 'datetime_created ~ "2017-01-01"'},
)
assert_equal(3, response_json['count'])

I didn't know how to write "from a given day" on the first place (datetime_created = "2017-01-01" is not equivalent, it gets items from one second "2017-01-01 00:00:00").

I found out that datetime_created ~ "2017-01-01" worked. However it stopped working with 0.8.6.

Any advice?

from djangoql.

interesting. I never thought about LIKE comparisons for datetime fields, so it was supported basically by accident :) However, this is an obviously useful case, so I added explicit support for it as well. Your case should be working back with v0.8.8 (please let me know if it doesn't)

from djangoql.

Works like a charm, thank you.

from djangoql.