SimpleDateFormat doesn't read MS correctly in Android 5.0 and zeros milliseconds for date fields about ormlite-android HOT 3 OPEN

Sorry for the long delay. Wow. Time under Android has been a real problem to keep up with. I've noted for some time that the SSSSSS should have been SSS but to change this would complete break backwards compatibility. You can certainly specify your own format although I'm not sure what .SSS would do with .321000 or .000321.

Maybe the right thing to do here is to support a persister that extends the DateStringType and sees if the date is a .SSSSSS and handles it but also handles .SSS and writes new dates as .SSS.

Comments?

from ormlite-android.

That will probably work for backwards compatibility. My only worry is the performance impact of doing the check on each read?

From what I've seen the reads of .321000 reads as .321 and 0.000321 reads as .000 when the date format is set to .SSS.

My solution to this was to simply use .SSS for all my date fields and upgrade my DB to the new format (always fun to write string manipulations in SQLite)

from ormlite-android.

The detection of the 6 versus 3 digits and the position of the zeros is nothing compared to the work needed to convert the string date into a java Date. I'm going to add it as a type.

from ormlite-android.