mirror of
https://github.com/doctrine/orm.git
synced 2026-03-23 22:42:18 +01:00
DDC-1464: Incompatibility between ORM 2.0 and DoctrineCommon 2.1 #1835
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @doctrinebot on GitHub (Oct 31, 2011).
Originally assigned to: @beberlei on GitHub.
Jira issue originally created by user javol:
When installing DoctrineORM 2.0.7 thru PEAR it now installs with DoctrineCommon 2.1.2 although it seems it is not compatible with it as I investigated it.
When executing queries built with query builder it throws error:
I found that the function
Doctrine\ORM\Mapping\ClassMetadataFactory->loadMetadata()does not return value as expected due to changes made to this between version 2.0 and 2.1 of the DoctrineCommon library.Workaround:
Uninstall DoctrineCommon and all what depends on it (DoctrineDBAL and DoctrineORM) and install DoctrineCommon manually with specified version < 2.1 (now 2.0.2) and do the same for DoctrineDBAL (now 2.0.7) and the then for DoctrineORM (now 2.0.7). Then all works fine.
Solution:
There should probably be specified maximum version DBAL and Common libraries < 2.1 in pear's package.xml of DoctrineORM for version < 2.1.
@doctrinebot commented on GitHub (Nov 8, 2011):
Comment created by @asm89:
Not a critical issue with the ORM itself, but rather its distribution, so I lowered the priority. Specifying the exact versions to install when using PEAR is indeed a good work-around for now.
@doctrinebot commented on GitHub (Mar 15, 2012):
Issue was closed with resolution "Won't Fix"