-
Notifications
You must be signed in to change notification settings - Fork 8.7k
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
solution: MySql 5.1.47 Time type error #1578
Labels
solution/MySQL
Record the solution to the MySQL problem
Comments
fescar-robot
added
DB: MySQL
Relate to seata MySQL
type: bug
Category issues or prs related to bug.
labels
Sep 3, 2019
zjinlei
removed
DB: MySQL
Relate to seata MySQL
type: bug
Category issues or prs related to bug.
labels
Sep 3, 2019
zjinlei
changed the title
solution: MySql Time type error
solution: MySql 5.1.47 Time type error
Sep 7, 2019
fescar-robot
added
DB: MySQL
Relate to seata MySQL
type: bug
Category issues or prs related to bug.
labels
Sep 7, 2019
zjinlei
removed
DB: MySQL
Relate to seata MySQL
type: bug
Category issues or prs related to bug.
labels
Sep 7, 2019
So will it update the plan in later versions? |
@wslongchen Recommended to replace the mysql version |
1 task
Closed
多谢提供方案,困扰了很久的问题 |
1 task
This was referenced Mar 8, 2020
1 task
using mysql-connector-java 5.1.39,garbled characters appear when reading database field type as json format data, be careful |
so it's a issue about seata , or a mysql connector issue? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Ⅰ. Issue Description
When using the mysql driver version 5.1.47, there are a variety of error cases that integrate seata, which can be solved by modifying the version (for example, using 5.1.39).
Case 1.Persistent Object contains LocalDateTime, use Mybatisplus to insert.
Case 2.Persistent Object contains java.util.Date, but seata is called setTimestamp method.
Ⅱ. Describe what happened
If there is an exception, please attach the exception trace:
Ⅲ. Describe what you expected to happen
Ⅳ. How to reproduce it (as minimally and precisely as possible)
Ⅴ. Anything else we need to know?
Ⅵ. Environment:
-mysql: 5.1.47
The text was updated successfully, but these errors were encountered: