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/DC-674 Doctrine 1 <p>Once the upgrade was done from Doctrine 1.2.1 to 1.2.2 we discovered that date related issues started to appear.<br/> With dates that are persisted in DB as NULL are translated to "0000-00-00" when retrieved from DB. This has occurred in multiple places and is quite worrying as there is a lot of dates in our project. This means that everywhere in our codebase where we check a datevalue in our Models is NULL we need also to check for the string literal "0000-00-00".</p> Zend Framework, Ubuntu 9.10, MySQL DC-674

NULL Dates are translated to '0000-00-00' after upgrading to 1.2.2

Bug Critical Open Unresolved Jonathan H. Wage Ville Itämaa Mon, 10 May 2010 07:59:54 +0000 Wed, 6 Oct 2010 06:29:40 +0000 1.2.1 1.2.2 1.2.1 1.2.2 Behaviors 0 1 <p>Are you able to reproduce this in a test case?</p> <p>We reverted to Doctrine 1.2.1 after realising the bug to confirm it was Doctrine 1.2.2 that was the cause for the problem. And as a result the records with NULL dates in the DB became NULL in the Models.<br/> But when using Doctrine 1.2.2, the NULL dates became '0000-00-00' in the Models.<br/> I don't have any other way to reproduce this error.</p> <p>Were you able to identity which changeset it was? You can read about creating test cases here <a href="http://www.doctrine-project.org/documentation/manual/1_2/en/unit-testing" class="external-link">http://www.doctrine-project.org/documentation/manual/1_2/en/unit-testing</a></p> <p>So far I am not able to reproduce the error you described.</p> <p>I'd like to fix this. Did you ever figure out which changeset introduced the issue? I've been trying to figure it out myself.</p> <p>With 1.2.3 this works for me fine with both TIMESTAMP and DATE fields.</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>YAML date_of_birth: type: date BASE MODEL $this-&gt;hasColumn('date_of_birth', 'date', null, array( 'type' =&gt; 'date', // try these two // 'notnull' =&gt; false, // 'default' =&gt; null )); </pre> </div></div> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>YAML exported_at: type: timestamp(25) notnull: false default: null # in this model I have everything to make sure it accepts and defaults to NULL BASE MODEL $this-&gt;hasColumn('exported_at', 'timestamp', 25, array( 'type' =&gt; 'timestamp', 'notnull' =&gt; false, 'length' =&gt; '25', )); </pre> </div></div> <p>You may try adding these to your YAML and (base) models</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre> YAML fieldname: . . . notnull: false default: null BASE MODEL $this-&gt;hasColumn('fieldname', . . . . . . 'notnull' =&gt; false, // &lt;&lt;&lt;&lt;&lt;&lt;&lt; // 'default' =&gt; null, // &lt;&lt;&lt; maybe, probably not needed )); </pre> </div></div> <p>I hope it helps.</p>