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

fix: qualify Emails::_createEmailQuery orderBy #3267

Conversation

msbit
Copy link
Contributor

@msbit msbit commented Sep 7, 2023

Add the table alias to the orderBy to avoid driver specific ambiguity in the generated SQL when joining against another table that also has a name column.

This is in line with States::_createStatesQuery, and should fix #3263.

Add the table alias to the `orderBy` to avoid driver specific ambiguity in
the generated SQL when joining against another table that _also_ has a `name`
column.

This is in line with `States::_createStatesQuery`, and should fix craftcms#3263.
@msbit msbit requested a review from a team as a code owner September 7, 2023 05:09
@lukeholder lukeholder merged commit ad18c52 into craftcms:develop Sep 7, 2023
@msbit msbit deleted the fix/3263-qualify-email-query-order-by-develop branch September 7, 2023 05:15
brandonkelly added a commit that referenced this pull request Oct 18, 2023
@lukeholder
Copy link
Member

@msbit thanks this is now in 4.3.1 out now.

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

Successfully merging this pull request may close these issues.

[3.x/4.x]: Emails::_createEmailQuery (and others) could be explicit about the orderBy
2 participants