-
Notifications
You must be signed in to change notification settings - Fork 5.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
same table alias is allowed in MySQL when tables come from different database #25364
Comments
seems a similar issue: #24663 |
@oops-lgtm Hi, may i ask that where do you meet this problem? |
When you create the table alias, MySQL holds the database name unchanged. It's against other databases like PostgreSQL, Oracle, and SQL Server. (They all throw out errors). |
For me, clearing the database name when you set an alias is a more comfortable behavior. And this can make our codes cleaner than be compatible with the MySQL. |
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
2. What did you expect to see? (Required)
no error
3. What did you see instead (Required)
ERROR 1066 (42000): Not unique table/alias: 'foo'
4. What is your TiDB version? (Required)
The text was updated successfully, but these errors were encountered: