Skip to content
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

shardingsphere4.0.0-RC1,Incorrect datetime value: 'now()' for column 'create_time' at row #2253

Closed
xfyang1989 opened this issue Apr 24, 2019 · 6 comments

Comments

@xfyang1989
Copy link

xfyang1989 commented Apr 24, 2019

shardingsphere4.0.0-RC1,report the following error:

Incorrect datetime value: 'now()' for column 'create_time' at row

ShardingSphere-SQL - Actual SQL: rw0 ::: insert into t_order(id, first_channel, biz_bill_no, orig_bill_no, warehouse_id, sku_code, change_inv_type, change_num, change_time, remark, create_time, create_person, update_time, update_person, is_deleted, version, sale_company, owner_id, bill_type, warehouse_code, status) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, 'now()', ?, 'now()', ?, 0, 0, ?, ?, ?, ?, ?) ::: [xx, xx, hh, hhh, xx, bb, xx, -6, 2019-04-24 09:22:54.825, null, xx, xx, xx, xx, 6, 0303, 0]

It seems that sharding treats the mysql now() function as a string.

@xfyang1989
Copy link
Author

This problem is OK in version 3.0.1

@codefairy08 codefairy08 self-assigned this Apr 24, 2019
@xfyang1989
Copy link
Author

Is Shardingsphere 4.0.0-RC1 having this problem?

@codefairy08
Copy link
Contributor

@xfyang1989 it also has this problem, i will fix it

codefairy08 added a commit to codefairy08/incubator-shardingsphere that referenced this issue Apr 25, 2019
@codefairy08
Copy link
Contributor

@xfyang1989 it was fixed,please have a try using latest dev branch code

@xfyang1989
Copy link
Author

3Q,When will these bugs be released to release a new version?

@xfyang1989
Copy link
Author

I feel that this 4.0.0-RC1 introduces a new bug, and these features are OK in version 3.0.1. I have used the smallest version of 4.0.0 in the project to keep the wrong version. . I feel that I will not continue to upgrade in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants