json_array columns should return null for null values

[wildlyinaccurate]

I guess this is a BC-break, but it fixes DBAL-446.

[doctrinebot]

Hello,

thank you for creating this pull request. I have automatically opened an issue
on our Jira Bug Tracker for you. See the issue link:

http://www.doctrine-project.org/jira/browse/DBAL-966

We use Jira to track the state of pull requests and the versions they got
included in.

[Ocramius]

Can't accept this bc break in 2.x, sorry.

[wildlyinaccurate]

That sucks, since it was marked as resolved in 2.3.3... What's the workaround then, a custom data type?

[Ocramius]

@wildlyinaccurate yep, for now, that's the solution :-\

[deeky666]

@wildlyinaccurate it is marked as resolved in 2.3.3 indeed but if you have a look at JsonArrayType in the 2.3.3 tag you will notice that the behaviours was the same as it is now. It still returns array() instead of null. As we unfortunately don't have a reference commit, I assume this was a misunderstanding of some kind.

[frickenate]

Could we maybe get an additional "json" or "json_object" type? "json_array" is a poor name to begin with, as we can store non-array data as well. You can store a boolean, integer, float, or string just fine in a json_array column. The only problem is that when this type was added, the assumption was made that people would only use this to store arrays. I have a config-based table where the value column should be json, yet I can't use json_array because of this null bug. I guess I'm off to figure out my first custom type.

[Ocramius]

I guess I'm off to figure out my first custom type.

I'd suggest the same as well: if we introduce a new json type now, then it's just going to be even more messy

[frickenate]

For the next person to come here looking for answers, I've posted a blog entry with the custom Json data type.