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-324 Doctrine DBAL <p>When using schema tool, Doctrine tries to infer the Doctrine type via the mapped types in Platform.<br/> It should first try to read from the comment; if found, ignore the Database type inference.</p> DBAL-324

SchemaManager should first look into comment instead of infer the type first.

Bug Major Open Unresolved All Guilherme Blanco Guilherme Blanco Fri, 17 Aug 2012 17:11:19 +0000 Tue, 14 May 2013 20:50:07 +0000 0 3 <p>Why is this a bug? Can you say some more about why we need to do this and what error occurs?</p> <p>This issue is strictly correlated to the commit I've done here: <a href="https://github.com/doctrine/dbal/commit/e25c774dde971dc4afd40648e9ccd0af53b34ce9" class="external-link">https://github.com/doctrine/dbal/commit/e25c774dde971dc4afd40648e9ccd0af53b34ce9</a></p> <p>Mainly, we may have legacy database that we do know how Doctrine should operate. Under this circumstance, we may want to add a comment to the field defining the Doctrine DBAL type.<br/> Even though after doing this, Doctrine still complains (in my situation, a SET column type) that it's unable to handle this column type.</p> <p>That happens because MySQL Schema Manager (and others) first looks for the column type:<br/> <a href="https://github.com/doctrine/dbal/blob/master/lib/Doctrine/DBAL/Schema/MySqlSchemaManager.php#L112" class="external-link">https://github.com/doctrine/dbal/blob/master/lib/Doctrine/DBAL/Schema/MySqlSchemaManager.php#L112</a><br/> <a href="https://github.com/doctrine/dbal/blob/master/lib/Doctrine/DBAL/Platforms/AbstractPlatform.php#L312" class="external-link">https://github.com/doctrine/dbal/blob/master/lib/Doctrine/DBAL/Platforms/AbstractPlatform.php#L312</a><br/> which automatically fails.</p> <p>But if we first try to look for the commented data type:<br/> <a href="https://github.com/doctrine/dbal/blob/master/lib/Doctrine/DBAL/Schema/AbstractSchemaManager.php#L884" class="external-link">https://github.com/doctrine/dbal/blob/master/lib/Doctrine/DBAL/Schema/AbstractSchemaManager.php#L884</a><br/> And forget about the rest if it finds one definition there, it would allow even unknown data types to be managed instead of forcing to define the DBAL Type compatible.</p> <p>This also applies for a type of yaml. <br/> Example:</p> <p> /** @Column(type="yaml") */<br/> protected $data = array();</p> <p>./scripts/doctrine orm:schema-tool:update --dump-sql<br/> ALTER TABLE meta CHANGE data data LONGTEXT NOT NULL;</p> <p>Very frustrating.... Might be related to <a href="http://www.doctrine-project.org/jira/browse/DBAL-42" class="external-link">http://www.doctrine-project.org/jira/browse/DBAL-42</a></p>