Datetimefield Queryset Returning None In Django
Solution 1:
not sure if you were able to figure this out, but I just had this problem and was able to fix it.
So, Django migrations were creating the column in the DB as datetime(6) instead of datetime. This was causing the Django models to fail to instantiate the Datetime object.
ALTERTABLE `my_table`
MODIFY COLUMN `created` datetime NOTNULL
After running that if fixed my issue. Maybe in your case you could try modifying to datetime(6) instead.
Solution 2:
We had this same issue popup while pushing code from local environment (Mac OS X) up to App Engine. While altering the fields like Alexander mentioned to be DATETIME instead of DATETIME(6) did start making them appear, we lost the microseconds. Ended up realizing that in local environment we were running MySQLdb 1.2.5 but when deploying to App Engine, even though we had specified "latest" as the version of MySQLdb, it was only pulling 1.2.4b4, hard-coding to 1.2.5 fixed the issue.
Solution 3:
Can you please try this solution:
queryset = list(ChangeMetrics.objects.filter(changed__isnull=False, date__isnull=False, version_id__isnull=False))
Solution 4:
EDIT : Try to move the databse out of your folder, then run python manage.py syncdb
and check if your database is created correctly according to the Models.
Doesn't work : Maybe you can try with this (I don't know if it works, I can't try it now) :
queryset = ChangeMetrics.objects.filter(changed!=None, date!=None, version_id!=None)
Solution 5:
This issue is caused by an outdated version of MySQL-python
not by Django or migrations system.
Using mysqlclient
(which is an updated fork of MySQL-python
) solves this problem.
Post a Comment for "Datetimefield Queryset Returning None In Django"