Github user yjhyjhyjh0 commented on the issue:
https://github.com/apache/nifi/pull/1983
Thanks for the review and feedback.
Iâve add your enhancement of handing time precision at milliseconds in
PutSQL.
Also I'm very willing to add a unit test for it.
However after some experiment, I figure out Derby DB has same behavior as
MySQL in Time type just like what you mentioned.
Iâve tested with derby, MySQL and PostgreSQL.
Only PostgreSQL will handle millisecond in Time type properly.
About the experiment, it store Time type well with value "00:01:01.111" in
PutSQL.
But once client fetch via jdbc of Derby.
It truncate the milliseconds.
(actually has different long value in client side) (java jdbc client and IJ
tool of derby)
So even with correct format to parse, the result in client side is
"00:01:01.000â.
Thus, I only update document to remind this situation instead of providing
a unit test for this format.
Please let me know if there is any problem.
Thanks for your patient.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
