Changes between Initial Version and Version 1 of Ticket #16408, comment 6


Ignore:
Timestamp:
Dec 19, 2012, 6:38:48 AM (12 years ago)
Author:
Mathijs Dumon

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #16408, comment 6

    initial v1  
    11This issue has re-appeared on django 1.5 b2.
    2 I checked the source files and it appears the spatialite backend is not patched for this issue in this version, and is still using compilers etc. from django.contrib.gis.db.models.sql.compile instead of django.contrib.gis.db.models.spatialite.compile (which is missing)
    3 merging the previous commits would solve it I guess...
     2
     3~~I checked the source files and it appears the spatialite backend is not patched for this issue in this version, and is still using compilers etc. from django.contrib.gis.db.models.sql.compile instead of django.contrib.gis.db.models.spatialite.compile (which is missing)
     4merging the previous commits would solve it I guess...~~
     5I stand corrected, this seems to have moved down, outside the spatialite backend into the base sql backend, my appologies. I can correctly get the values as datatime objects in a shell.
     6The but occurs when using the 'date_hierarchy' on an admin model
Back to Top