-
Notifications
You must be signed in to change notification settings - Fork 8.8k
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
The datasource proxy's problem #5291
Comments
Please provide the original field column names and sql and seata proxy generated sql and log details |
trace info:
|
Stack information as above |
This is a strange problem, |
I just removed |
Actually, disable |
Yes |
This is a bug, but the information you provided is not quite accurate |
@ZenkieBear please give me more information about druid dependency. |
We're using druid-spring-boot-starter
1.2.11 version
ZENKIE
…---Original---
From: ***@***.***>
Date: Mon, Feb 6, 2023 20:08 PM
To: ***@***.***>;
Cc: "Zenkie ***@***.******@***.***>;
Subject: Re: [seata/seata] The datasource proxy's problem (Issue #5291)
@ZenkieBear please give me more information about druid dependency.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
The problem exists and I will fix it, but the problem with select sql I did not reproduce successfully |
The select sql has no problem, it's just a guess. It could have worked right! :)
ZENKIE
…---Original---
From: ***@***.***>
Date: Mon, Feb 6, 2023 21:23 PM
To: ***@***.***>;
Cc: "Zenkie ***@***.******@***.***>;
Subject: Re: [seata/seata] The datasource proxy's problem (Issue #5291)
The problem exists and I will fix it, but the problem with select sql I did not reproduce successfully
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Thank you!
ZENKIE
…---Original---
From: ***@***.***>
Date: Mon, Feb 6, 2023 21:23 PM
To: ***@***.***>;
Cc: "Zenkie ***@***.******@***.***>;
Subject: Re: [seata/seata] The datasource proxy's problem (Issue #5291)
The problem exists and I will fix it, but the problem with select sql I did not reproduce successfully
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Ⅰ. Issue Description
Seata's datasource proxy's sql checker has a problem, it'll replace the character '`'.
Ⅱ. Describe what happened
There's a field named 'all' in our table. But all is a sql keyword. We use MyBatisPlus, I used put a @TableFiled("
`all`
") annotation to avoid the sql syntax error, and it works.Today, I imorted seata to our project. When I execute the sql include field 'all', a SQLSyntaxErrorException has been threw. It gave a message:
You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'all,xxx FROM t_access_record ' at line 1
. Seems, seata's datasource proxy replaced the characted '`'.Normally, mybatis-plus don't replace the character. But it has dirty-reading problem. Seata resolve these distrubut-system's problem, but its datasource proxy is not ideal.
Ⅲ. Describe what you expected to happen
I want to have an option to decide whether the data source agent should replace some characters.
Ⅳ. How to reproduce it (as minimally and precisely as possible)
`all`
")' to the fieldⅤ. Anything else we need to know?
No.
Ⅵ. Environment:
The text was updated successfully, but these errors were encountered: