http://www.doctrine-project.org/jira This file is an XML representation of an issue en-us 5.2.7 850 21-02-2013 http://www.doctrine-project.org/jira/browse/DBAL-385 Doctrine DBAL <p>When use Array type and NULL value</p> <p>set null give in database 'N;' (serialise(null))<br/> need NULL </p> DBAL-385

Null need set to NULL in array type

Bug Major Resolved Can't Fix All Benjamin Eberlei Ivan Borzenkov Sat, 17 Nov 2012 11:14:33 +0000 Sun, 25 Nov 2012 15:44:45 +0000 Sun, 25 Nov 2012 12:16:32 +0000 0 2 <p>This would be a BC Break and cannot be done anymore. You can add your own array type that has this behavior.</p> <p>It will not be a loss of backward compatibility.<br/> Now if we have an empty array, that is stored serialized NULL, but the default value for NULL instead of N;<br/> 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</p> <p>The field might be NOT NULL, that is what might break BC.</p> <p>and if field is null?</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> /** * @<span class="code-keyword">var</span> array $yandexReg * * @ORM\Column(name=<span class="code-quote">"yandexReg"</span>, type=<span class="code-quote">"array"</span>, nullable=<span class="code-keyword">true</span>) */ <span class="code-keyword">private</span> $yandexReg; </pre> </div></div> <p>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.</p>