-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Type names with backslashes cause failing upgrades #2926
Comments
Observed this as well, possibly platform-dependent (double-)quoting issue, needs investigation. |
ostrolucky
added a commit
to ostrolucky/dbal
that referenced
this issue
Nov 11, 2018
ostrolucky
added a commit
to ostrolucky/dbal
that referenced
this issue
Nov 11, 2018
ostrolucky
added a commit
to ostrolucky/dbal
that referenced
this issue
Nov 11, 2018
Fixed by #3330 |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm planning ahead and starting to use FQCNs as custom doctrine type getName implementation, as well as registering them under that name with Type::addType. Sadly, it seems SQL comments with backslashes are somehow not matched with the desired value, and the upgrade command fails with :
This is slightly different than what I described in doctrine/orm#6752 .
Here is the column comment I have:
The text was updated successfully, but these errors were encountered: