2👍
✅
I think this can be readily explained:
- sqlite3 lacks explicit datetime support as ‘bobince’ points out in the comments above
- django.db.backends.sqlite3 works around this via storing as text in ISO-8601 format
- but this is not part of JDBC support, which expects real datetime support
Note there is an outstanding bug to add complete sqlite3 support to Jython. I just adjusted the milestone for that bug to 2.7.2 (could be later). Such support is something we have wanted to do for a while, although it’s a bit complicated because it’s not just a question of using JDBC.
For the time being, this likely means you would to either do your own workaround (don’t know scope); or switch to a database like MySQL or Apache Derby (small footprint like sqlite3, but with support for datetimes).
Source:stackexchange.com