-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Millisecond information for java.sql.Time
is lost when converting to/from LocalTime
#74
Labels
Comments
jeff303
added a commit
to metabase/metabase
that referenced
this issue
Jun 15, 2021
…imezone-handling-test` closer to passing Reported issue with loss of millisecond portion to/from java.sql.Time: `dm3/clojure.java-time#74
jeff303
added a commit
to metabase/metabase
that referenced
this issue
Jun 17, 2021
…imezone-handling-test` closer to passing Reported issue with loss of millisecond portion to/from java.sql.Time: `dm3/clojure.java-time#74
jeff303
added a commit
to metabase/metabase
that referenced
this issue
Jul 23, 2021
…imezone-handling-test` closer to passing Reported issue with loss of millisecond portion to/from java.sql.Time: `dm3/clojure.java-time#74
This happens due to the implementation of |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Consider the following REPL session, in which version
0.3.2
of the library is being used (as per the deps.edn guide here).Notice that the millisecond portion (
456
) is lost. In principle, though, it is possible to build thejava.sql.Time
instance to have that information:The same problem occurs in reverse as well:
Again, it's possible to preserve that information (probably more elegantly than this):
The text was updated successfully, but these errors were encountered: