ulwfcyvi opened a new issue #13139:
URL: https://github.com/apache/shardingsphere/issues/13139
## Bug Report
### Which version of ShardingSphere did you use?
#### sharding-proxy:5.0.0-beta
### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
#### ShardingSphere-Proxy
### Expected behavior
#### Return the correct timestamp
### Actual behavior
#### Return 2000-01-01
### Reason analyze (If you can)
####
org.apache.shardingsphere.db.protocol.postgresql.packet.command.query.binary.bind.protocol.PostgreSQLTimeBinaryProtocolValue#write
. This method should return microseconds
### Steps to reproduce the behavior, such as: SQL to execute, sharding rule
configuration, when exception occur etc.
#### PostgreSqlDB field type is timestamp(6) and
org.apache.shardingsphere.proxy.frontend.postgresql.authentication.PostgreSQLAuthenticationEngine#processPasswordMessage
Add a line of cod, 【context.write(new
PostgreSQLParameterStatusPacket("integer_datetimes", "on"));】
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
