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

Do not assume "SET" as top level when preceded with "CHARACTER" #150

Merged
merged 2 commits into from
Jan 24, 2025

Conversation

mvorisek
Copy link
Contributor

close #149

@mvorisek mvorisek changed the title Do not assume "SET" as top level when preceded with "CHARSET" Do not assume "SET" as top level when preceded with "CHARACTER" Jan 23, 2025
@greg0ire greg0ire added bug Something isn't working CI labels Jan 24, 2025
@derrabus derrabus added this to the 1.5.2 milestone Jan 24, 2025
@derrabus derrabus merged commit d6d00ab into doctrine:1.5.x Jan 24, 2025
10 checks passed
@mvorisek mvorisek deleted the CHARACTER_SET_149 branch January 24, 2025 11:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working CI
Projects
None yet
Development

Successfully merging this pull request may close these issues.

The CHARACTER SET keyword is split with a new line
3 participants