You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that millisecond precision throws an error at writing out this data as xpt, as an Int representation is assumed with a Second interval. Is this necessary? If so, probably a more informative error would be better
Ah it actually appears that the file is written, but the error happens when showing the resulting ReadStatTable. I can also read the file back in with t = ReadStatTables.readstat("test.xpt") and again only showing that object fails, not the reading itself.
@jkrumbiegel Thank you for reporting! I realize that since Julia DateTime is internally represented as Int64, conversion to integer has to happen at some point. The best thing for me to do seems to be having some rounding to the closest Millisecond. This will be addressed in #39 and come with v0.3.1 release soon.
junyuan-chen
changed the title
Millisecond precision for DateTimesInexactError for floating-point date/time values
Apr 2, 2024
It seems that millisecond precision throws an error at writing out this data as xpt, as an Int representation is assumed with a
Second
interval. Is this necessary? If so, probably a more informative error would be betterThe text was updated successfully, but these errors were encountered: