-
-
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
Stop using the deprecated json_array
type internally
#2782
Stop using the deprecated json_array
type internally
#2782
Conversation
Since it was deprecated.
3f56f92
to
c611df2
Compare
c611df2
to
0b50739
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@lcobucci any user-side change required here? Parch seems good otherwise.
@Ocramius I think it shouldn't required but TBQH I'm not sure. |
YOLO, 🚢 |
json_array
type internally
@Ocramius @lcobucci changing the default i have an old column using
Applying the diff does nothing. the same diff persists afterwards. Only way for the user to fix this is to change the column type from |
@bendavies that's sad news, sorry for causing this issue. I'll be checking the options to fix the problem caused by 31d0128. Thanks for letting us know of that |
Thanks @lcobucci! |
this requires changing which type requires SQL comment hint. currently, json_array says it does not require a SQL comment hint when native json type is supported in the platform, because platforms would map the native type to it. But as you changed it, you have to change the comment hint requirement here |
On 31d0128 we made JsonType the default one, which caused some unexpected results with the comparator. This tests validates that if users have a JSON column but are using the JsonArrayType we'll just add a comment to the column. Reference: doctrine#2782
@bendavies @stof I think I've managed to fix the reported BC-break on #2855, could you please check (it's still WIP, though)? |
On 31d0128 we made JsonType the default one, which caused some unexpected results with the comparator. This tests validates that if users have a JSON column but are using the JsonArrayType we'll just add a comment to the column. Reference: doctrine#2782
On 31d0128 we made JsonType the default one, which caused some unexpected results with the comparator. This tests validates that if users have a JSON column but are using the JsonArrayType we'll just add a comment to the column. Reference: doctrine#2782
According to BC-break in doctrine/dbal doctrine/dbal#2782 (comment)
On 31d0128 we made JsonType the default one, which caused some unexpected results with the comparator. This tests validates that if users have a JSON column but are using the JsonArrayType we'll just add a comment to the column. Reference: doctrine#2782
On 31d0128 we made JsonType the default one, which caused some unexpected results with the comparator. This tests validates that if users have a JSON column but are using the JsonArrayType we'll just add a comment to the column. Reference: doctrine#2782
On 31d0128 we made JsonType the default one, which caused some unexpected results with the comparator. This tests validates that if users have a JSON column but are using the JsonArrayType we'll just add a comment to the column. Reference: doctrine#2782
On 31d0128 we made JsonType the default one, which caused some unexpected results with the comparator. This tests validates that if users have a JSON column but are using the JsonArrayType we'll just add a comment to the column. Reference: doctrine#2782
No description provided.