DBAL-385: Null need set to NULL in array type #1575

Closed
doctrinebot opened this Issue Nov 17, 2012 · 6 comments

2 participants

@doctrinebot

Jira issue originally created by user ivan1986:

When use Array type and NULL value

set null give in database 'N;' (serialise(null))
need NULL

@doctrinebot

Comment created by @beberlei:

This would be a BC Break and cannot be done anymore. You can add your own array type that has this behavior.

@doctrinebot

Issue was closed with resolution "Can't Fix"

@doctrinebot

Comment created by ivan1986:

It will not be a loss of backward compatibility.
Now if we have an empty array, that is stored serialized NULL, but the default value for NULL instead of N;
On the part of php will not be any differences - the inverse transform is the same, from the database, we combined the two into a single value, the more accurate in terms of DB

@doctrinebot

Comment created by @beberlei:

The field might be NOT NULL, that is what might break BC.

@doctrinebot

Comment created by ivan1986:

and if field is null?


/****
 * @var array $yandexReg
 *
 * @ORM\Column(name="yandexReg", type="array", nullable=true)
 */
private $yandexReg;

@doctrinebot

Comment created by @beberlei:

Well in this case it works obviously, however the Type API doesn't have access to that information. Thats why I meant you should build your own array type and override the internal implementation. This is explained in the Mapping Fields Document of ORM and in the Type Documentation of DBAL.

@doctrinebot doctrinebot added the Bug label Dec 6, 2015
@beberlei beberlei was assigned by doctrinebot Dec 6, 2015
@doctrinebot doctrinebot closed this Dec 6, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment