Doctrine Project

[DBAL-157] Exception given when updating schema

Fri, 18 Nov 2011 19:52:07 +0000

Been experimenting with Symfony2 past days, and somehow managed to generate an Exception in the MySqlSchemaManager Classes of Doctrine.

I've build my schema once, the next time i run the command i'm receiving following error:

[ErrorException]
Notice: Undefined index: default in /Users/chris/Sites/Symfony/vendor/doctrine-dbal/lib/Doctrine/DBAL/Schema/MySqlSchemaManager.php line 157

i can't figure out an error in my classes.

When i drop the database table, i can re-run the command again without exception.. even though another run it will throw it up again.

I've checked the code in line #157, and adpted it slightls:

'default' => $tableColumn['default'],

modified:
'default' => (isset($tableColumn['default'])) ? $tableColumn['default'] : null,

Can anyone confirm this issue?

Greetings,
Chris

[DBAL-171] PARAM_INT_ARRAY / PARAM_STR_ARRAY depends of parameter order

Fri, 18 Nov 2011 16:45:43 +0000

Named parameters appears to be treated as ordered parameters, when using PARAM_INT_ARRAY or PARAM_STR_ARRAY:

$query = $em->createQuery('
SELECT f FROM Foo f
WHERE a = :a
AND b IN (:b)
');

$query->setParameters(array(
    'b' => array(1,2,3),
    'a' => 1,
));

Notice that in the query the parameter :a appears before :b. And I call ->setParameters() with :b before :a.

When running this, I get an error from Doctrine/DBAL/SQLParserUtils::expandListParameters:119 saying that the second parameter of array_merge() is not an array.

When setting the parameters in the same order than they appear in the query, it works:

$query->setParameters(array(
    'a' => 1,
    'b' => array(1,2,3),
));

This is unexpected, as I'm using named parameters; the order should not matter.

[DBAL-144] Oracle tables without indices are not handled during convert - this behavior should be tolerant since Oracle does not require indicies.

Mon, 14 Nov 2011 22:44:07 +0000

While it is good practice to always have at least one index defined on every table, in some cases (such as temporary tables) indices are not necessary. Oracle does not enforce creating indices for every table, and it is common to create some tables without them. The Table.php (line 556) method throws an exception if an index is not found for a given table. It's obvious there are ramifications for findByPK( ) auto-generated methods - these should be generated for every case where PK exists to accommodate Oracle and tolerate variances from accepted best-practices with most other database platforms.

[DBAL-181] [Oracle] RAW Type

Mon, 14 Nov 2011 20:24:01 +0000

Missing type raw from OraclePlatform::initializeDoctrineTypeMappings.

The Symfony2 task doctrine:schema:update throws Unknown database type raw requested, Doctrine\DBAL\Platforms\OraclePlatform may not support it..

The attached patch seems to fix it, but I don't know if something more to be done.

[DBAL-168] orm:schema-tool:update will fail if if public scheme has a domains table (PostgreSQL)

Mon, 14 Nov 2011 19:12:41 +0000

If I create a table 'domains' in the default scheme and execute the update procedure of the schema tool, it will throw a PDOException (SQLSTATE[21000]: Cardinality violation: 7 ERROR: more than one row returned by a subquery used as an expression)

I've traced the error to the following statement, which is created by Doctrine\DBAL\Platforms\PostgreSqlPlatform->getListTableForeignKeysSQL():

SELECT r.conname, pg_catalog.pg_get_constraintdef(r.oid, true) as condef
                  FROM pg_catalog.pg_constraint r
                  WHERE r.conrelid =
                  (
                      SELECT c.oid
                      FROM pg_catalog.pg_class c, pg_catalog.pg_namespace n
                      WHERE c.relname = 'domains'
                        AND n.oid = c.relnamespace
                  )
                  AND r.contype = 'f'

This returns two oids because there are two relations with the name domains. One is my table and the other is a view in the information_scheme scheme.

The same problem should occur with the other information_scheme relations.

[DBAL-158] Sqlite Platform doesn't set a proper mapping for "double precision" to act as float.

Sun, 30 Oct 2011 18:54:26 +0000

I have a column in an entity, defined as "float" type.
When I run my phpunit tests (which are defined to use sqlite, whereas my production and development environment uses mysql), I get the following exception:

Doctrine\DBAL\DBALException: Unknown database type double precision requested, Doctrine\DBAL\Platforms\SqlitePlatform may not support it

Looking at AbstractPlatform.php, line 1972, function "getFloatDeclarationSQL" returns 'DOUBLE PRECISION'.
Where other platforms have in their "initializeDoctrineTypeMappings" method a mapping such as:

'double precision' => 'float',

, SqlitePlatform.php doesn't have such a mapping.

[DBAL-172] QueryBuilder joins are omitted if the table alias is not present in the "from" clause

Sun, 30 Oct 2011 18:54:07 +0000

When using the QueryBuilder, joins that refer to table aliases from other joins get omitted. Only those joins that refer to table aliases from the "from" clause get included.

See http://stackoverflow.com/questions/7331117/doctrines-dbal-query-builder-omitts-some-joins