[GitHub] [incubator-shardingsphere] lightning-pro opened a new issue #3640: Timestamp miss milliseconds when reading from sharding-proxy

[GitBox <gi...@apache.org>]

lightning-pro opened a new issue #3640: Timestamp miss milliseconds when reading from sharding-proxy
URL: https://github.com/apache/incubator-shardingsphere/issues/3640
 
 
   ### Which version of ShardingSphere did you use?
   4.0.0-RC4 compile by myselft from the source code
   ### Which project did you use? Sharding-JDBC or Sharding-Proxy?
   Sharding-Proxy
   ### Expected behavior
   read the timestamp value from sharding-proxy should contains the milliseconds
   ### Actual behavior
   miss the milliseconds when reading from sharding-proxy
   ### Reason analyze (If you can)
   maybe there is type converstion or byte read bug in sharding-proxy?
   ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.
   Just any database client tools to connect to the proxy to select query a reacord with timestamp values with milliseconds in real database tables
   ### Example codes for reproduce this issue (such as a github link).
   just a very easy select statement test can reproduce this issue.
   this is the followup testing after the issue #3550 fixed by #3632 
   I have left an comment there for the easy reference

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services