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

Revert "Workaround SELECT ... ORDER BY (SELECT 1) related bug in Oracle's MySQL implementation, that can lead to completely wrong data being returned. (#1850)" #1870

Merged
merged 1 commit into from
Mar 8, 2024

Conversation

lauxjpn
Copy link
Collaborator

@lauxjpn lauxjpn commented Mar 8, 2024

Reverts #1850.

ORDER BY (SELECT 1) is not equivalent to ORDER BY 1.
See #1849 (comment) for more information.

Fixes #1849 (comment)

…le's MySQL implementation, that can lead to completely wrong data being returned. (PomeloFoundation#1850)"

(cherry picked from commit 0f66b72)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Using SELECT ... ORDER BY (SELECT 1) can lead to the return of unexpected data using Oracle MySQL releases
1 participant