-
Notifications
You must be signed in to change notification settings - Fork 6.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
v5.4.0 There may be a bug in "left join". #28014
Comments
Hi @Cindyxin228 , what's your sharding_db configuration (dataSources and rules)? |
|
Hi~I copied my configration in the comment just now. |
Hi @strongduanmu Could you help to have a look at it? |
Hi @Cindyxin228, can you open |
Hi~
and
I'm sorry very much that it seems I didn't find valuable information. But I can share how it leads to the question above.
After configuration, copy the sql I give in the first comment and then execute. Then the question arises. And if you still need that I give information about the actual sql. Could you please tell me how to open that and get the actual sql. Thanks very much. |
Excuse me, is there any progress on this issue recently |
There's something wrong with "left join"
My version is 5.4.0.
When I tried to use "left join", I found that a column which should be in the result is missing. Here's the more specific explanation.
I execute the following sql statements in mariaDB and in sharding_db, the virtual database processed through shardingsphere-proxy.
And the result in mariaDB is as follows.
The result in sharding_db is as follows.
The result in mariaDB is correct, and we can see the results have a column missing in sharding_db. Therefore, I think there's maybe a bug here.
The text was updated successfully, but these errors were encountered: