Doctrine Project

[DDC-1172] Schema tool does not drop sequences on table drop for PostgreSql platform

Fri, 1 Mar 2013 16:26:15 +0000

When recreating database using

$schemaTool->dropSchema($metaDatas);
$schemaTool->createSchema($metaDatas);

the second line fails with error that the sequence "tbl_id_seq" already exists. It's because the sequence is created without an owner column and schema tool doesn't include "drop sequence" statements in the drop SQL.

I've created a patch which fixes the problem for my environment. Revision numbers in patch is from the local SVN. Doctrine base is 2.0.5.

[DDC-250] ArrayCollection Key Column @indexBy

Dependency — Thu, 11 Oct 2012 12:34:56 +0000

To be honest I feel like I saw this mentioned somewhere, but after looking around I couldn't find it, so I'll just post this anyway.

I'd like the ability to set a property as the associative key on ArrayCollections. This functionality could probably be done in a PostLoad by iterating over the objects, but it seems like ArrayCollection should be able to handle this functionality already, it's just a matter of modifying the mapper/parser.

Example:

/**
 * @Entity
 */
class Object
{
//... $id column and anything else ...
    /**
     * @OneToMany(targetEntity="Param", mappedBy="object")
     */
    protected $params;
//...
    public function getParam($name)
    {
         return $this->params[$name];
    }
}

/**
 * @Entity
 */
class Param
{
    /**
     * @ManyToOne(targetEntity="Object")
     * @JoinColumn(name="object_id", referencedColumnName="id", nullable="false")
     */
    protected $object;
    /**
     * @Column(type="string")
     */
    protected $name;
    /**
     * @Column(type="string")
     */
    protected $value;
}

If you were able to specify an ArrayCollection key column then you would be able to have functions like getParam without having to loop over the objects in the collection. Something like:

 @OneToMany(targetEntity="Param", mappedBy="object", collectionKey="name")

[DDC-1209] DateTime (and other custom object types) cannot be used in primary key (singular or composite)

Fri, 14 Sep 2012 01:22:00 +0000

This bug was encountered using a DateTime type as an @Id, but it appears that it will affect any type of custom data type if it is an object.

Doctrine\ORM\Id\AssignedGenerator checks to see if the key is an object. If so it does a look up in the identity map to find the object, but in the case of DateTime it will not find it and throws an exception. It is appears this is the case for both singular and composite keys as shown in the attached test.

Offending code: https://github.com/doctrine/doctrine2/blob/master/lib/Doctrine/ORM/Id/AssignedGenerator.php#L52

Test case forthcoming.

[DDC-945] Crashing Bug: BasicEntityPersister::_getSelectColumnListSQL returns empty list, thus generating wrong SQL

Sat, 14 Apr 2012 05:48:44 +0000

I have a situation where Doctrine generates a wrong SQL query and crashes with an exception.

The userland code calls the EntityManager::merge method.

The query generated looks like "SELECT FROM SomeTable", meaning it has no select column list, and therefore it's plainly wrong.

The entity I am trying to merge back into the entity manager is a regular entity with state detached. The class has a column which is declared as ID and filled with an autogenerated value, three regular columns, and a one-to-many relationship. The to-many-relationship causes BasicEntityPersister::loadOneToManyCollection() to be called, which in turn calls BasicEntityPersister::_getSelectEntitiesSQL, which then calls BasicEntityPersister::_getSelectColumnListSQL, which wrongly returns an empty string, thus leading to the corrupt query without a select column list being generated. The target entity of the one-to-many relationship is a mapped superclass, which has an ID (again with autogenerated values), and a many-to-one relationship inversing the one in the first entity. Further fields depend on its exact type as determined by the inheriting entities, but it will always have some.

Here is the exception, up to the point where the trace leaves the ORM:

exception 'PDOException' with message 'SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'FROM VersionedDataObject t0' at line 1' in /var/www/invoiceCreator/src/thirdPartyComponents/doctrine/Doctrine/DBAL/Connection.php:577 Stack trace: #0 /var/www/invoiceCreator/src/thirdPartyComponents/doctrine/Doctrine/DBAL/Connection.php(577): PDO->query('SELECT FROM Ve...') #1 /var/www/invoiceCreator/src/thirdPartyComponents/doctrine/Doctrine/ORM/Persisters/BasicEntityPersister.php(1173): Doctrine\DBAL\Connection->executeQuery('SELECT FROM Ve...', Array) #2 /var/www/invoiceCreator/src/thirdPartyComponents/doctrine/Doctrine/ORM/UnitOfWork.php(1984): Doctrine\ORM\Persisters\BasicEntityPersister->loadOneToManyCollection(Array, Object(persistentData\model\versioning\InputComponentDataVersion), Object(Doctrine\ORM\PersistentCollection)) #3 /var/www/invoiceCreator/src/thirdPartyComponents/doctrine/Doctrine/ORM/PersistentCollection.php(207): Doctrine\ORM\UnitOfWork->loadCollection(Object(Doctrine\ORM\PersistentCollection)) #4 /var/www/invoiceCreator/src/thirdPartyComponents/doctrine/Doctrine/ORM/UnitOfWork.php(1441): Doctrine\ORM\PersistentCollection->initialize() #5 /var/www/invoiceCreator/src/thirdPartyComponents/doctrine/Doctrine/ORM/UnitOfWork.php(1323): Doctrine\ORM\UnitOfWork->doMerge(Object(persistentData\model\versioning\InputComponentDataVersion), Array) #6 /var/www/invoiceCreator/src/thirdPartyComponents/doctrine/Doctrine/ORM/EntityManager.php(520): Doctrine\ORM\UnitOfWork->merge(Object(persistentData\model\versioning\InputComponentDataVersion))

This one is a blocker by user standards. The error means that it is impossible to use Doctrine in long-running batch jobs like in my situation, because it does not support merging certain detached objects back into the entity manager at all, while at some point they need to be detached for virtual memory capacity reasons.

[DDC-1024] the EntityGenerator generate getters and setters for properties of the parent class

Wed, 4 Jan 2012 11:24:41 +0000

when using the EntityGenerator to generate getters and setters of two classes mapped with annotations, one inheriting from the other, the EntityGenerator generates getters and setters for the properties of the parent class in the child class too. This occurs since the recent EntityGenerator changes (as it did not care about inheritance before).
I suppose this is due to the fact that the getters and setters of the parent class are not yet generated when handling the child class.

I haven't try if it works well when using XML or YAML for the mapping.

[DDC-1281] ORM uses BasicEntityPersister instead of JoinedSubclassPersister on a JOINED inheritance

Mon, 1 Aug 2011 22:19:46 +0000

Hi,
I have these classes: https://gist.github.com/1085518/58b5424bc0ab5af1ae65421fe832e7a1b45533cf (read the comments to see the stracktrace)

If I try:
$entity = $em->find('Usuario', $id);
$entity->getPessoaFisica()->getId();
I got this error: Class does not exist.

This is looking weird because, analyzing the stacktrace, the ORM loads the proxy through the BasicEntityPersister instead of JoinedSubclassPersister.

I've been discussed about this on: http://groups.google.com/group/doctrine-user/browse_thread/thread/190dc2c4b768ae13#

Regards,
Daniel Lima

[DDC-1309] Doctrine_Collection toArray() does not return results of table joins.

Mon, 1 Aug 2011 01:51:09 +0000

e.g.
$doctrineCollection = Doctrine_Query::create()
->from('Table1 a')
->innerJoin('a.Table2 b ON a.id = b.id')
->execute();

$doctrineCollection->toArray() will return only the contents of Table1. However, $doctrineCollection->getFirst()->toArray() will return the results of Table1 + an additional key named 'Table2' which returns the join result from Table2.

It does not make sense for the collection hydration to differ to that of the objects in the collection.

[DDC-1104] Require statement in AnnotationDriver.php can cause PHP Fatal error

Sun, 31 Jul 2011 10:09:03 +0000

The require statement in Doctrine/ORM/Mapping/Driver/AnnotationDriver.php causes troubles in some cases. Imagine the situation when you're creating your own class loader which maps all classes and loads all requested classes lazily. When it loads any class from DoctrineAnnotations.php before loading AnnotationDriver and this class is loaded later, you get: PHP Fatal error: Cannot redeclare class ....

Changing require to require_once solves the problem.

Pull request: https://github.com/doctrine/doctrine2/pull/45

[DDC-1226] OneToOne Unidirectional entities not persisting

Duplicate — Sat, 23 Jul 2011 15:56:05 +0000

We have the following three entities:

User
Participant
Profile

... Users and Participants are two distinctly different things in our system and each has a Profile. Currently we use OneToOne unidirectional associations to "map" the User to it's Profile and a Participant to it's Profile. So far (2.0) we've been able to do the following:

$profile = $user->getProfile();
$profile->setLastName('Doe');
$em->persist($profile);
$em->flush();

...and the profile is saved. In 2.1 rc1 this no longer works.

After some testing it was determined that 2.1 is requiring that our Profile refer back to each object (bidirectional). Now, this may not be the best example but imagine we had another entity that wanted to make use of a Profile, we'd rather not have to explicitly add the reference back for each entity that wants to use it just to get it persisted.

Again, in 2.0 our setup worked fine and so far I've been unable to find any documentation pointing to this sort of thing.

[DDC-1238] Proxy query executed, but object not initialized

Mon, 4 Jul 2011 21:44:11 +0000

Proxy query executed, but object not initialized

[DDC-1239] Using a repository with composite keys generates invalid SQL

Thu, 30 Jun 2011 19:04:58 +0000

Invalid SQL is generated when using composite keys along with Repository methods (fineOneBy, etc). Everything works properly when using createQuery() to generate DQL manually.

Working:
$q = $this->_em
->createQuery(
"SELECT c,c2,g FROM Entity\OAuth\Consumer c LEFT JOIN c.group g LEFT JOIN c.clinic c2 WHERE c.key = '{$consumer_key}'");
$this->_consumer = $q->getSingleResult();

Invalid:
$this->_consumer = $this->_em->getRepository('Entity\OAuth\Consumer')
->findOneBy(array('key' => $consumer_key));

Generated SQL for "invalid" method:
SELECT ... FROM oauth_consumer t0 LEFT JOIN groop t10 ON t0.groupId = t10.id LEFT JOIN company t17 ON t0.companyId = t17.id LEFT JOIN clinic t28 ON t0.dsid = t28.dsid t0.rid = t28.rid LEFT JOIN user t50 ON t0.userId = t50.id WHERE t0.`key` = ?

Notice the missing AND in the query above. I've attached the entities in question.

[DDC-1203] Single Table Inheritance - Discriminator Column is not populated

Thu, 30 Jun 2011 18:58:33 +0000

I have the following class inheritance; if I have the mapped super class in there, the discriminator column is not populated; if I remove it, it is correctly set.

/**
 * @ORM\Entity
 * @ORM\Table(name = "a")
 * @ORM\ChangeTrackingPolicy("DEFERRED_EXPLICIT")
 * @ORM\InheritanceType("SINGLE_TABLE")
 * @ORM\DiscriminatorColumn(name="type", type="string", length=20)
 * @ORM\DiscriminatorMap({
 *     "c"   = "C",
 *     "d"   = "D"
 * })
 */
abstract class A { }

/**
 * @ORM\MappedSuperClass
 */
abstract class B extends A { }

/**
 * @ORM\Entity
 */
class C extends B { }

/**
 * @ORM\Entity
 */
class D extends B { }

[DDC-1233] Minor spellcheck in UnitOfWork

Tue, 28 Jun 2011 20:32:02 +0000

On UnitOfWork, line 580:
. " on the relationship. If you cannot find out which entity casues the problem"

should be:

. " on the relationship. If you cannot find out which entity causes the problem"

[DDC-1231] In ObjectHydrator->_getEntity(...) looking for the discriminator should be in uppercase

Tue, 28 Jun 2011 19:41:01 +0000

On line 204:
$discrColumn = $this->_rsm->metaMappings[$this->_rsm->discriminatorColumns[$dqlAlias]];

$this->_rsm->discriminatorColumns[$dqlAlias] is in lowercase, whereas $this->_rsm->metaMappings[$this->_rsm->discriminatorColumns[$dqlAlias]] is in uppercase.

$discrColumn cannot be assigned.

A simple fix could be:
$discrColumn = $this->_rsm->metaMappings[strtoupper($this->_rsm->discriminatorColumns[$dqlAlias])];

[DDC-1230] entity state is not set to STATE_REMOVED when removing an entity

Tue, 28 Jun 2011 19:39:28 +0000

The UnitOfWork never sets the state to STATE_REMOVED in the map when scheduling an entity for delete. This means that the UnitOfWork will never tell you that the entity is in STATE_REMOVED when asking for its state but will return STATE_MANAGED

[DDC-1218] Generator disappear with mappedSuperclass and in others common inheritance's cases

Mon, 27 Jun 2011 09:35:27 +0000

With mapped superclass the id lost autoincrement. I've test with yaml and annotation this is the same.

An example with yaml entities :

 
Document:
  type: mappedSuperclass
  fields:
    mimetype: { type: string, length: 255 }
    filename: { type: string, length: 255 }

Image:
  type: entity
  fields:
    id: { type: integer, id: true, generator: { strategy: AUTO } }

The id in the table Image lost autoincrement.

[DDC-1224] QueryBuilder delete issues CREATE TEMPORARY TABLE error on PostgreSQL

Sun, 26 Jun 2011 08:13:31 +0000

When I try to issue a delete an Class Table Inheritance Entity using QueryBuilder and I'm using schemas on tablename (for Postgres), I got the following error from postgres:

SQLSTATE[42P16]: Invalid table definition: 7 ERROR: temporary tables cannot specify a schema name

This occurs because Doctrine\ORM\Mapping\ClassMetadataInfo::getTemporaryIdTableName() returns just "$this->table['name'] . '_id_tmp'", and when my entity is declared with @Table(name="feed.tb_feed"), obviously I will got error.

Temporary tables are created in a special schema in Postgres, and I'm thinking to convert the tablename from the class metadata from feed.tb_feed to feed_tb_feed into the getTemporaryIdTableName method with a single str_replace. That works for Postgres, but I don't mind what can happen in another DBMS.

Any suggestions?

[DDC-1223] STI Inheritance Mapping Exception suggests to mark Entity abstract when initialization is not required, how to realize this?

Sat, 25 Jun 2011 10:22:49 +0000

I have an abstract PHP class 'PartyAbstract' that uses Single Table Inheritance with a discriminator map to distinguish between a number of classes that extend the 'PartyAbstract' class. The 'PartyAbstract' class itself is not an entry in that discriminator map. Annotations are used to define the discriminator map.

 
/**
* @Entity
* @Table(schema="public", name="party")
* @InheritanceType("JOINED")
* @DiscriminatorColumn(name="discriminator", type="integer")
* @DiscriminatorMap({
* "1" = "Project\Entity\Party\PartyType1",
* "2" = "Project\Entity\Party\PartyType2",
* "3" = "Project\Entity\Party\PartyType3"
* })
abstract class PartyAbstract{}

As of version 2.1.0-rc1, the following exception is thrown:

 
"Entity 'Project\Entity\PartyAbstract' has to be part of the descriminator map of 'Project\Entity\PartyAbstract' to be properly mapped in the inheritance hierachy. If you want to avoid instantiation of this type mark it abstract."

My question is: how can I mark this Entity abstract? I DO want to be able to count the complete number of Parties, but instantiation of the PartyAbstract class is never required. The use of @MappedSuperclass is not allowed here, or together with the @Entity annotation...

PS: also not that the message in the exception contains two typo's

'descriminator' vs 'discriminator'
'hierachy' vs 'hierarchy'

[DDC-1159] From string used as object in QueryBuilder.php

Sat, 25 Jun 2011 09:19:10 +0000

In QueryBuilder.php at line 956, $from is used as an object when it's in fact a string.

[DDC-1221] Fatal Error when building a query using ->add() instead of ->from()

Sat, 25 Jun 2011 09:16:42 +0000

When creating a query using $qb->add('from', ...) instead of $qb->from(...) a fatal error is thrown when building the DQL query line 989 of the QueryBuilder because this line assumes it has a Doctrine\ORM\Query\Expr\From instance whereas it gets a string.

Note that a similar issue was fixed for $qb->getRootAlias: http://www.doctrine-project.org/jira/browse/DDC-1140

[DDC-1227] On 2.1 upgrade QueryBuilder incompatability getAlias() when using ''->add('select', 'sample')->add('from', 'Samply sample') instead of ->select('sample')->from('Sample', 'sample')

Sat, 25 Jun 2011 08:27:53 +0000

In queryBuilder if I use the add function when adding components to the query I get an error like this :

Fatal error: Call to a member function getAlias() on a non-object in /usr/local/zend/share/pear/Doctrine/ORM/QueryBuilder.php on line 989

sample code is

$this->em->createQueryBuilder()
		    ->add('select', 'sample')
		    ->add('from', 'Sample sample')
		    ->getQuery()
		    ->execute()

it works with the following:

$this->em->createQueryBuilder()
		    ->select('sample')
		    ->from('Sample', 'sample')
		    ->getQuery()
		    ->execute()

I apologize if this is a duplicate ticket. I would like to see this fixed in the final release of 2.1 before installing it in our production environment.

[DDC-1156] MappedSuperclass not allowed in the middle of an inheritance hierarchy

Sat, 25 Jun 2011 08:21:21 +0000

For a Class Table Inheritance mapping configuration, an intermediate MappedSuperclass causes a 'noInheritanceOnMappedSuperClass' mapping exception to be thrown by Doctrine\ORM\Mapping\ClassMetadataFactory::loadMetadata() (line 329). However, the MappedSuperclass only contains some simple properties and no inheritance configuration such as DiscriminatorMap or DiscriminatorColumn settings. The MappedSuperclass DOES extend the upper class in the hierarchy that contains this information using annotations, maybe this way it inherits this inheritance configuration.

The documentation state that a MappedSuperclass can occur in the middle of a inheritance hierarchy.
http://www.doctrine-project.org/docs/orm/2.0/en/reference/inheritance-mapping.html#mapped-superclasses

PS: this mapping seemed to be working fine for me using Doctrine 2.0.4 and Doctrine 2.0.5, further inspection showed that this is not the case. Persistence of an Entity fails, Doctrine wants to update a sequence of the persisted Entity, that does not exist as it is a Class Table Inheritance
PPS: this applies for the 2.1.0-BETA1 release, which is not yet available to create an issue for.

[DDC-1222] Composite Primary Key is not recognized

Tue, 21 Jun 2011 18:58:11 +0000

I have the following mapping:

class TopicTranslation
{
    /**
* @ORM\Id
* @ORM\ManyToOne(targetEntity="Topic")
*/
    private $topic;

    /**
* @ORM\Id
* @ORM\Column(type="string", length=5)
*/
    private $locale;
}

Doctrine will only use "locale" as primary key for the table. I would expect it to use "topic_id" and "locale" instead.

[DDC-1017] mysql error when renaming a manyToOne property

Sun, 19 Jun 2011 08:59:39 +0000

These are my initial properties with annotations:

// Task.php
/**

@ManyToOne(targetEntity="Maia\Model\User", inversedBy="tasks")
*/
protected $user;

// User.php
/**

@OneToMany(targetEntity="Maia\Model\Task", mappedBy="user")
*/
protected $tasks;

At this stage, everythings works fine.

However when I try to rename the property $user to $author like so:

// User.php
/**

@OneToMany(targetEntity="Maia\Model\Task", mappedBy="author")
*/
protected $tasks;

and change the corresponding entity like this:
/**

@ManyToOne(targetEntity="Maia\Model\User", inversedBy="tasks")
*/
protected $author;

and then try to update my database using the './doctrine orm:schema-tool:update --force' command, I get the following error:
[PDOException]
SQLSTATE[HY000]: General error: 1025 Error on rename of './maia/#sql-508_2be' to './maia/Task' (errno: 150)

in the database 'information_schema' and then tabel 'key_column_usage' I find this line:
CONSTRAINT_CATALOG Null
CONSTRAINT_SCHEMA maia
CONSTRAINT_NAME Task_ibfk_1
TABLE_CATALOG Null
TABLE_SCHEMA maia
TABLE_NAME Task
COLUMN_NAME user_id
ORDINAL_POSITION 1
POSITION_IN_UNIQUE_CONSTRAINT 1
REFERENCED_TABLE_SCHEMA maia
REFERENCED_TABLE_NAME User
REFERENCED_COLUMN_NAME id

I had to perform the following query on my database before I was able to update:
ALTER TABLE User DROP FOREIGN KEY Task_ibfk_1;

Maybe I am doing something wrong, this is my first project with Doctrine, but I tweeted about the error and somebody asked me to create a ticket so here it is.

[DDC-887] Schema tool can throw errno 121 when creating or dropping indexes

Sun, 19 Jun 2011 08:59:10 +0000

When changing the model in such a way that the schema tool tries to create or drop an index which is also a foreign key an error is sometimes thrown like:

[PDOException]
SQLSTATE[HY000]: General error: 1025 Error on rename of '.\mydb#sql-10d8_19' to '.\mydb\auth' (errno: 121)

This seems to be caused by MySQL trying to re-use indexes and I think it depends on exactly what has happened before in this table so I can't give an exact case to reproduce. However, it seems to be InnoDB specific and I'm pretty sure its this bug: http://bugs.mysql.com/bug.php?id=15317

[DDC-1211] Expr::literal problem with numeric value 0

Sun, 19 Jun 2011 08:27:51 +0000

Hi,

I'm using master branch of Doctrine 2. Including an Expr with a numeric 0 value (not a string):

$value = 0;

$qb->expr()->gte($field, $qb->expr()->literal($value));

Expr::literal method will return an empty string ('') instead of '0', which causes that this expression be something like:

entity.myField >=

instead of:

entity.miField >= '0''

This makes the query fail. Tracking the issue down I've found this on Expr\Base::add method:

    public function add($arg)
    {
         if ( ! empty($arg) || ($arg instanceof self && $arg->count() > 0)) {
            // If we decide to keep Expr\Base instances, we can use this check
            if ( ! is_string($arg)) {
                $class = get_class($arg);

                if ( ! in_array($class, $this->_allowedClasses)) {
                    throw new \InvalidArgumentException("Expression of type '$class' not allowed in this context.");
                }
            }

            $this->_parts[] = $arg;
        }
    }

The problem is that empty function returns true if you pass '0', so a call to Expr\Base::add would end on NOT adding '0' to $this->_parts array. That's why it finally returns ''.

I wanted to make the fix for this but I'm having issues running the phing build task. Which are the steps to follow to run the tests? Running phing build task I get on the "test" task:

Could not create task/type: 'nativephpunit'. Make sure that this class has been declared using taskdef / typedef.

Thanks!

[DDC-1214] Call to undefined method Doctrine\ORM\Tools\Console\Command\SchemaTool\UpdateCommand::getFullName()

Sun, 19 Jun 2011 08:05:43 +0000

The getFullName() method has been removed from the latest Symfony\Component\Console\Command\Command class and is causing the above error on line 131 of UpdateCommand.php

[DDC-1212] Exception of mapping of ID generation strategy

Thu, 16 Jun 2011 21:10:29 +0000

Hi all,

After updating today Doctrine 2 from master branch I'm getting:

Entity of type "Entity" is missing an assigned ID. The identifier generation strategy for this entity requires the ID field to be populated before EntityManager#persist() is called. If you want automatically generated identifiers instead you need to adjust the metadata mapping accordingly.

Was there a change on the mapping of ID generation strategy? I was using a commit of the master branch from 1 o 2 weeks ago and it was working ok. I took a look at the repo for changes on the last days but I couldn't find anything related to this.

I paste the mapping and entities here:

Element:

/**
 * @ORM\MappedSuperclass
 */
abstract class Element
{
    /**
     * @ORM\Id
     * @ORM\Column(type="integer")
     * @ORM\GeneratedValue(strategy="IDENTITY")
     */
    protected $id;
}

File:

/**
 * @ORM\Entity
 * @ORM\Table(name="file")
 * @ORM\InheritanceType("JOINED")
 * @ORM\DiscriminatorColumn(name="discriminator", type="string")
 * @ORM\DiscriminatorMap({
        "image"  = "Image",
    })
 */
abstract class File extends Element
{
     // Fields
}

And Image:

/**
 * @ORM\Entity
 * @ORM\Table(name="image")
 */
class Image extends File
{
     // Fields
}

Thanks in advance!

[DDC-1190] Update the doctrine mapping schma in such way it will allow extending the final xml with data from different vendors

Wed, 15 Jun 2011 20:48:06 +0000

I've already made a PR
https://github.com/doctrine/doctrine2/pull/64

[DDC-1196] EntityGenerator: made it work with Doctrine Common 3.0.x

Wed, 15 Jun 2011 20:47:03 +0000

The entity generator does not work with the new Doctrine Common 3.0.x.

Issue is reported here in Symfony: https://github.com/symfony/symfony/issues/1083

PR that fixes the issue here: https://github.com/doctrine/doctrine2/pull/61

[DDC-1204] Single Table Inheritance - Columns of one hierarchy are dropped

Wed, 15 Jun 2011 20:27:53 +0000

In the following example, the columns of the classes B, C, D are not in the database schema. Only those of the classes A and E.

/**
 * @ORM\Entity
 * @ORM\Table(name = "a")
 * @ORM\ChangeTrackingPolicy("DEFERRED_EXPLICIT")
 * @ORM\InheritanceType("SINGLE_TABLE")
 * @ORM\DiscriminatorColumn(name="type", type="string", length=20)
 * @ORM\DiscriminatorMap({
 *     "c"   = "C",
 *     "d"   = "D",
 *     "e"   = "E"
 * })
 */
abstract class A { }

/**
 * @ORM\Entity
 */
abstract class B extends A { }

/**
 * @ORM\Entity
 */
class C extends B { }

/**
 * @ORM\Entity
 */
class D extends B { }

/**
 * @ORM\Entity
 */
class E extends A { }

[DDC-1168] Implemented tableName -> className and columnName -> fieldName mapping in DatabaseDriver.

Sat, 11 Jun 2011 11:02:05 +0000

As requested a ticket to remind you of looking at this pull request: https://github.com/doctrine/doctrine2/pull/59.

The patch enables custom naming of entities and fieldnames when re-engineering from the database. It can be used when the mapping is done with a script, not by the commandline (yet?).

[DDC-1179] Allow to specify namespace prefix in combination with --from-database

Sat, 11 Jun 2011 11:01:58 +0000

See https://github.com/symfony/symfony/issues/1119#comment_1247346

[DDC-1184] ORM\Id\AssignedGenerator try to current() on non-array

Sat, 11 Jun 2011 08:46:49 +0000

// Doctrine\ORM\AssignedGenerator::generate at line 54

$identifier[$idField] = current($em->getUnitOfWork()->getEntityIdentifier($value));

$value may also be new, so getEntityIdentifier returns NULL and current(NULL) generates an E_WARNING.

[DDC-1176] Error on proxy loading with foreign Key

Sat, 11 Jun 2011 07:46:20 +0000

Look at this thread:http://groups.google.com/group/doctrine-user/browse_thread/thread/2a03a6aea43428d6

This entity class configuration:

class IndividualsStatus
{
    /**
     * @var Individuals
     *
     * @Id
     * @ManyToOne(targetEntity="Individuals", inversedBy="diagnosers", cascade={"persist","refresh","remove"})
     * @JoinColumns({
     *   @JoinColumn(name="individuals_id", referencedColumnName="id")
     * })
     */
    private $individuals;

    /**
     * @var Diagnosers
     *
     * @Id
     * @ManyToOne(targetEntity="Diagnosers", inversedBy="individuals", cascade={"persist","refresh"})
     * @JoinColumns({
     *   @JoinColumn(name="diagnosers_id", referencedColumnName="id")
     * })
     */
    private $diagnosers;

    /**
    * @var smallint $status
    *
    * @Column(name="status_individuals", type="smallint")
    */
    private $statusIndividuals;

    [...]
}

class Individuals
{
    /**
     * @var Users
     *
     * @OneToOne(targetEntity="Users", cascade={"persist","detach","merge","refresh","remove"}, orphanRemoval=true)
     * @JoinColumns({
     *   @JoinColumn(name="users_id", referencedColumnName="id", unique=true)
     * })
     */
    private $users;

    /**
     * @var Advertisements
     *
     * @OneToMany(targetEntity="Advertisements", mappedBy="individuals")
     */
    private $advertisements;

    /**
     * @var IndividualsStatus
     *
     * @OneToMany(targetEntity="IndividualsStatus", mappedBy="individuals", cascade={"refresh", "remove", "persist"})
     * @joinColumns({
     *   @JoinColumn(name="individuals_id", referencedColumnName="id")
     * })
     */
    private $diagnosers;

  [...]
}

class Diagnosers
{
    /**
     * @var Users
     *
     * @OneToOne(targetEntity="Users", cascade={"persist","remove","detach","merge","refresh"})
     * @JoinColumns({
     *   @JoinColumn(name="users_id", referencedColumnName="id", unique=true)
     * })
     */
    private $users;

    /**
     * @var Pros
     *
     * @OneToOne(targetEntity="Pros", cascade={"persist","remove","detach","merge","refresh"})
     * @JoinColumns({
     *   @JoinColumn(name="pros_id", referencedColumnName="id", unique=true)
     * })
     */
    private $pros;

    /**
     * @var Reports
     *
     * @OneToMany(targetEntity="Reports", mappedBy="diagnosers", cascade={"refresh", "remove"})
     */
    private $reports;

    /**
     * @var IndividualsStatus
     *
     * @OneToMany(targetEntity="IndividualsStatus", mappedBy="diagnosers", cascade={"refresh", "remove", "persist"})
     * @joinColumns({
     *   @JoinColumn(name="diagnosers_id", referencedColumnName="id")
     * })
     */
    private $individuals;
}

Note that in individuals, the relation called "Diagnosers" refered to IndividualsStatus entity.
Note that in diagnosers, the relation called "Individuals" refered to IndividualsStatus entity.

When I execute this DQL request:
   $qb->select(array('i', 'iss', 'u')) 
           ->from('IndividualsStatus', 'iss') 
           ->join('iss.individuals', 'i') 
           ->join('i.users', 'u') 
           ->where('iss.diagnosers = ?1') 
           ->andWhere('iss.individuals = ?2') 
           ->setParameters(array(1 => $idDiag, 2 => $id));

I retrieve an IndividualsStatus entity:

object(stdClass)[149] 
  public '__CLASS__' => string 'IndividualsStatus' (length=37) 
  public 'individuals' => 
    object(stdClass)[148] 
      public '__CLASS__' => string 'Individuals' (length=31) 
      public 'reference' => string '451' (length=3) 
      public 'maxAdvertisements' => null 
      public 'role' => int 2 
      public 'id' => int 8 
      public 'users' => string 'Users' (length=25) 
      public 'advertisements' => string 'Array(0)' (length=8) 
      public 'diagnosers' => string 'Array(1)' (length=8) 
      public 'ownedReports' => string 'Array(0)' (length=8) 
      public 'reports' => string 'Array(0)' (length=8) 
      public '_em' => null 
  public 'diagnosers' => 
    object(stdClass)[154] 
      public '__CLASS__' => string 'Proxies 
\OpengroupeEntitiesDiagnosersProxy' (length=61) 
      public 'id' => string '19' (length=2) 
  public 'statusIndividuals' => int 1 
  public '_em' => null

Now i want to access to the "Diagnosers" relation of the Individuals:
\Doctrine\Common\Util\Debug::dump($individualsStatus->getIndividuals()->getDiagnosers());

In my database, this individuals got 2 diagnosers attached, but only 1 is dumped.
For getting the 2, i have to select the Diagnosers relation into my Dql request:

   $qb->select(array('i', 'iss', 'u', 'd')) 
           ->from('IndividualsStatus', 'iss') 
           ->join('iss.individuals', 'i') 
           ->join('i.diagnosers', 'd') 
           ->join('i.users', 'u') 
           ->where('iss.diagnosers = ?1') 
           ->andWhere('iss.individuals = ?2') 
           ->setParameters(array(1 => $idDiag, 2 => $id));

Then if i do \Doctrine\Common\Util\Debug::dump($individualsStatus->getIndividuals()->getDiagnosers())
I have my 2 diagnosers display.

[DDC-1194] Problem using Instance of feature

Fri, 10 Jun 2011 16:41:08 +0000

Hi, i get this error message when executing a query with INSTANCE OF.
Notice: Undefined index: \model\PeopleTaskRecommendFriends in /usr/share/php/Doctrine/ORM/Query/SqlWalker.php on line 1626

The query to be executed is this:

                $query = $this->_em->createQuery("SELECT pt
                                          FROM \model\PeopleTask pt
                                          WHERE pt instance of \model\PeopleTaskRecommendFriends
                                          ");

The query actually being executed is this:

SELECT t0_.int_people_task_id AS int_people_task_id0, t0_.int_people_id AS int_people_id1, t0_.dtm_creation AS dtm_creation2, t0_.bit_completed AS bit_completed3, t0_.vch_names AS vch_names4, t0_.int_task_type_id AS int_task_type_id5 FROM tbl_xref_people_task t0_ WHERE (t0_.int_task_type_id = '') AND t0_.int_task_type_id IN ('1', '2')

The first problem is that for some reason its translating the query with a wrong where clause, so of course no data is returned.

Here is the model

------------------------------------------ Base class----------------------------------------
/**
 * @Entity(repositoryClass="repository\PeopleTaskRepository")
 * @InheritanceType("SINGLE_TABLE")
 * @DiscriminatorColumn(name="int_task_type_id", type="integer")
 * @DiscriminatorMap({1 = "PeopleTaskRecommendFriends", 2 = "PeopleTaskAddBadge"})
 * @Table(name="tbl_xref_people_task")
 */
abstract class PeopleTask extends BaseModel {
 
    /**
     * @Id
     * @GeneratedValue
     * @Column(type="integer") */
    protected $int_people_task_id;
 
    /** @Column(type="integer") */
    protected $int_people_id;
 
    /** @Column(type="datetime") */
    protected $dtm_creation;
 
    /** @Column(type="bit")*/
    protected $bit_completed;
 
    /** @Column(length=255) */
    protected $vch_names;
 
}
 
----------------------------------------------------Children class-----------------------------------------------
 
/**
 * @Entity(repositoryClass="repository\peopleTask\PeopleTaskRecommendFriendsRepository")
 */
class PeopleTaskRecommendFriends extends PeopleTask {
 /* some methods */
 
}

[DDC-1163] entity persister gets superclasses' metadata for proxied subclass entity

Sun, 5 Jun 2011 14:27:34 +0000

Using class table inheritance:

When a proxy for a subclass-entity is registered at the unit of work and another entity, which references that entities' superclass, is added or removed, the employed entity persister gets/uses the superclasses' metadata.

If the change-set of the referenced entity contains fields only defined in the subclass, the persister will create bogus SQL because it has no column names or data types: UPDATE table SET = ? WHERE id = ?

The attached test case is stand-alone, creating an SQLite in-memory DB (sorry, I'm not familiar with your test suite).

Only the path to Doctrine must be adapted at the top of 'run_test.php'.
The file 'SubclassPropertyBugTest.php' also contains a more detailed description.

[DDC-1192] fix undefined variable in join-column section of xml driver

Sun, 5 Jun 2011 12:51:00 +0000

$name is undefined, It might be that the fix is as simple as foreach ($manyToOneElement->

{'join-columns'}->{'join-column'} as $name => $joinColumnElement) {
but I'm not sure

if (isset($manyToOneElement->{'join-column'})) {
$joinColumns[] = $this->_getJoinColumnMapping($manyToOneElement->{'join-column'});
} else if (isset($manyToOneElement->{'join-columns'}

)) {
foreach ($manyToOneElement->

{'join-columns'}

{'join-column'}

as $joinColumnElement) {
if (!isset($joinColumnElement['name']))

{ $joinColumnElement['name'] = $name; }

$joinColumns[] = $this->_getJoinColumnMapping($joinColumnElement);
}
}

[DDC-1173] Fatal error when a listener resets an object in onFlush and recompute the changeset

Sun, 5 Jun 2011 11:34:21 +0000

When a listener resets an entity during onFlush and recompute the changeset (setting it to null as there is no changes), the following triggering of preUpdate fails as PreUpdateEventArgs would get null as third argument which is forbidden

[DDC-1191] fix the notices when converting between different mappings

Sun, 5 Jun 2011 10:29:14 +0000

https://github.com/doctrine/doctrine2/pull/62
https://github.com/doctrine/doctrine2/pull/63

[DDC-1193] cascadeRemove misses associations due to proxy not being initialized

Dependency — Sun, 5 Jun 2011 08:08:55 +0000

Let's assume you have two One-to-One relations A>B>C (all include cascade remove). You are deleting object A, while object B is not initialized (and so it will be a proxy). In that case the object C is not deleted because UOW misses relation B>C since proxy of B is not initialized

[DDC-733] Implement a way of forcing a PersistentCollection to initialize itself

Dependency — Sun, 5 Jun 2011 06:45:24 +0000

Currently the only way to force an uninitialized collection to load itself is to call one of its methods (e.g. ->count()).

Roman suggested something like $em->initialize($collection)

[DDC-1141] DisconnectedClassMetadataFactory forbids direct XML-to-SQL conversion

Sun, 5 Jun 2011 06:22:01 +0000

Doctrine\ORM\Tools\DisconnectedClassMetadataFactory::newClassMetadataInstance() returns instances of ClassMetadataInfo, while the parent returns instances of ClassMetadata. This creates problems when using SchemaTool to create a schema from an XML mapping for instance:

Fatal error: Call to undefined method Doctrine\ORM\Mapping\ClassMetadataInfo::getQuotedTableName() 
in path/to/Doctrine/ORM/Tools/SchemaTool.php on line 133

This is because schemaTool expects ClassMetadata objects, while it got ClassMetadataInfo objects.

My setup:

 
$config = new Configuration();
$config->setMetadataCacheImpl(new \Doctrine\Common\Cache\ArrayCache);
$driverImpl = new XmlDriver(__DIR__ . '/fixtures');
$config->setMetadataDriverImpl($driverImpl);
$config->setProxyDir(__DIR__ . '/Proxies');
$config->setProxyNamespace('Proxies');
$connectionOptions = array(
    'driver' => 'pdo_sqlite',
    'path' => 'database.sqlite'
);
$em = \Doctrine\ORM\EntityManager::create($connectionOptions, $config);
$cmf = new DisconnectedClassMetadataFactory();
$cmf->setEntityManager($em);

$metadatas = $cmf->getAllMetadata() // array of ClassMetadataInfo and not ClassMetadata

I think Doctrine\ORM\Tools\DisconnectedClassMetadataFactory::newClassMetadataInstance() should return a ClassMetadata instance.

[DDC-1080] AbstractHydrator ->_gatherRowData using wrong metadata info

Tue, 17 May 2011 21:43:03 +0000

The following worked in a previous version but after upgrading to the latest to fix the security issue, I got an issue.

I will first start with the setup:

MySQL

CREATE TABLE `bar` (
  `barID` int(11) NOT NULL AUTO_INCREMENT,
  `barTitle` varchar(45) DEFAULT NULL,
  PRIMARY KEY (`barID`)
) ENGINE=InnoDB AUTO_INCREMENT=5 DEFAULT CHARSET=utf8;

CREATE TABLE `foo` (
  `fooID` int(11) NOT NULL AUTO_INCREMENT,
  `fooTitle` varchar(45) DEFAULT NULL,
  PRIMARY KEY (`fooID`)
) ENGINE=InnoDB AUTO_INCREMENT=3 DEFAULT CHARSET=utf8;

CREATE TABLE `fooBar` (
  `fooID` int(11) NOT NULL,
  `barID` int(11) NOT NULL,
  `orderNr` int(11) DEFAULT NULL,
  PRIMARY KEY (`fooID`,`barID`),
  KEY `b` (`barID`),
  KEY `f` (`fooID`),
  CONSTRAINT `f` FOREIGN KEY (`fooID`) REFERENCES `foo` (`fooID`) ON DELETE CASCADE ON UPDATE NO ACTION,
  CONSTRAINT `b` FOREIGN KEY (`barID`) REFERENCES `bar` (`barID`) ON DELETE CASCADE ON UPDATE NO ACTION
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

INSERT INTO `bar` (barID,barTitle) VALUES (1,'bar title 1');
INSERT INTO `bar` (barID,barTitle) VALUES (2,'bar title 2');
INSERT INTO `bar` (barID,barTitle) VALUES (3,'bar title 3');
INSERT INTO `bar` (barID,barTitle) VALUES (4,'bar title 4');

INSERT INTO `foo` (fooID,fooTitle) VALUES (1,'foo title 1');
INSERT INTO `foo` (fooID,fooTitle) VALUES (2,'foo title 2');

INSERT INTO `fooBar` (fooID,barID,orderNr) VALUES (1,1,0);
INSERT INTO `fooBar` (fooID,barID,orderNr) VALUES (1,2,1);
INSERT INTO `fooBar` (fooID,barID,orderNr) VALUES (1,3,3);

Foo.php

<?php
/**
 * @Entity
 * @Table(name="foo")
 */

class Application_Model_Foo
{
	
	/**
	 * @Id 
	 * @Column(name="fooID", type="integer")
	 * @GeneratedValue(strategy="AUTO")
	 */
	protected $_fooID;
	
	/**
	 * @Column(name="fooTitle", type="string")
	 */
	protected $_fooTitle;
	
	/**
	 * @OneToMany(targetEntity="Application_Model_FooBar", mappedBy="_foo",
	 * cascade={"persist"})
	 * @OrderBy({"_orderNr"="ASC"})
	 */
	protected $_fooBars;

	public function __construct ()
	{
		$this->_fooBars = new \Doctrine\Common\Collections\ArrayCollection();
	}
	
	/**
	 * @return the $fooID
	 */
	public function getFooID ()
	{
		return $this->_fooID;
	}

	/**
	 * @return the $fooTitle
	 */
	public function getFooTitle ()
	{
		return $this->_fooTitle;
	}

	/**
	 * @return the $fooBars
	 */
	public function getFooBars ()
	{
		return $this->_fooBars;
	}

	/**
	 * @param field_type $fooID
	 */
	public function setFooID ($fooID)
	{
		$this->_fooID = $fooID;
	}

	/**
	 * @param field_type $fooTitle
	 */
	public function setFooTitle ($fooTitle)
	{
		$this->_fooTitle = $fooTitle;
	}

	/**
	 * @param field_type $fooBars
	 */
	public function setFooBars ($fooBars)
	{
		$this->_fooBars = $fooBars;
	}


}

Bar.php

<?php
/**
 * @Entity
 * @Table(name="bar")
 */

class Application_Model_Bar
{
	
	/**
	 * @Id 
	 * @Column(name="barID", type="integer")
	 * @GeneratedValue(strategy="AUTO")
	 */
	protected $_barID;
	
	/**
	 * @Column(name="barTitle", type="string")
	 */
	protected $_barTitle;
	
	/**
	 * @OneToMany(targetEntity="Application_Model_FooBar", mappedBy="_bar",
	 * cascade={"persist"})
	 * @OrderBy({"_orderNr"="ASC"})
	 */
	protected $_fooBars;

	public function __construct ()
	{
		$this->_fooBars = new \Doctrine\Common\Collections\ArrayCollection();
	}
	/**
	 * @return the $barID
	 */
	public function getBarID ()
	{
		return $this->_barID;
	}

	/**
	 * @return the $barTitle
	 */
	public function getBarTitle ()
	{
		return $this->_barTitle;
	}

	/**
	 * @return the $fooBars
	 */
	public function getFooBars ()
	{
		return $this->_fooBars;
	}

	/**
	 * @param field_type $barID
	 */
	public function setBarID ($barID)
	{
		$this->_barID = $barID;
	}

	/**
	 * @param field_type $barTitle
	 */
	public function setBarTitle ($barTitle)
	{
		$this->_barTitle = $barTitle;
	}

	/**
	 * @param field_type $fooBars
	 */
	public function setFooBars ($fooBars)
	{
		$this->_fooBars = $fooBars;
	}


}

FooBar.php

<?php
/**
 * @Table(name="fooBar")
 * @Entity
 */
class Application_Model_FooBar
{

	/**
	 * @ManyToOne(targetEntity="Application_Model_Foo")
	 * @JoinColumn(name="fooID", referencedColumnName="fooID")
	 * @Id
	 */
	protected $_foo = null;

	/**
	 * @ManyToOne(targetEntity="Application_Model_Bar")
	 * @JoinColumn(name="barID", referencedColumnName="barID")
	 * @Id
	 */
	protected $_bar = null;

	/**
	 * @var integer orderNr
	 * @Column(name="orderNr", type="integer", nullable=false)
	 */
	protected $_orderNr = null;

	/**
	 * Retrieve the foo property
	 *
	 * @return Application_Model_Foo
	 */
	public function getFoo()
	{
		return $this->_foo;
	}

	/**
	 * Set the foo property
	 *
	 * @param Application_Model_Foo $foo
	 * @return Application_Model_FooBar
	 */
	public function setFoo($foo)
	{
		$this->_foo = $foo;
		return $this;
	}

	/**
	 * Retrieve the bar property
	 *
	 * @return Application_Model_Bar
	 */
	public function getBar()
	{
		return $this->_bar;
	}

	/**
	 * Set the bar property
	 *
	 * @param Application_Model_Bar $bar
	 * @return Application_Model_FooBar
	 */
	public function setBar($bar)
	{
		$this->_bar = $bar;
		return $this;
	}

	/**
	 * Retrieve the orderNr property
	 *
	 * @return integer|null
	 */
	public function getOrderNr()
	{
		return $this->_orderNr;
	}

	/**
	 * Set the orderNr property
	 *
	 * @param integer|null $orderNr
	 * @return Application_Model_FooBar
	 */
	public function setOrderNr($orderNr)
	{
		$this->_orderNr = $orderNr;
		return $this;
	}


}

When I execute the following code

IndexController.php

$foo = $this->_em->find('Application_Model_Foo', 1);
$fooBars = $foo->getFooBars();
var_dump(count($fooBars));

I expect "3" as output. But I get "1".

There seems to be an issue with the metadata or the used fieldname in the _gatherRowData in the AbstractHydrator.

The following is a dump of $classMetadata = $this->_em->getClassMetadata($this->_rsm->aliasMap[$cache[$key]['dqlAlias']]);

abstractHydrator

$fieldName = $this->_rsm->metaMappings[$key]; is "fooID" or "barID"

After assigning $cache[$key]['isIdentifier'] = $classMetadata->isIdentifier($fieldName); you get false back.

So you check for fooID / barID in the array

[identifier] => Array
        (
            [0] => _foo
            [1] => _bar
        )

what of course is false because they aren't in the array.

When I set the flag $cache[$key]['isIdentifier'] to true for the 2 fields, I get an output of 3 as expected.

So the fieldname is wrong or the identifier list is wrong.

[DDC-694] Add info Command that shows Entities and Mapping Directories

Sun, 15 May 2011 18:19:07 +0000

We should add an command to get information about the doctrine project:

List all entities
List all mapping directories/mapping drivers
Maybe configuration stuff?

[DDC-1059] Add helper for ResultSetMapping

Sun, 15 May 2011 17:31:20 +0000

Building a ResultSetMapping yourself is tedious work, it can be simplified by passing ClassMetadata instances, so that the RSM even changes when the Entity Metadata changes.

Two use-cases:

1. Add Entity X as Root Entity
2. Add Entity X as Fetch Joined Entity of parent entity Y

[DDC-1029] renaming "load()" in proxy to "__load()"

Reference — Fri, 13 May 2011 03:23:57 +0000

It would be really great if the method "load" is renamed to something more protected like "__load" or "_doctrineOdmLoad" like it has done for public properties
public $__dm;
public $__identifier;
public $isInitialized = false;
Because otherwise if a referenced document has the same method "load" it causes error like this

"Fatal error: Cannot redeclare Proxies\ProjectProxy::load() in /projects/tbi_doctrine/tmp/doctrine/proxies/ProjectProxy.php on line 46"

[DDC-1122] Parsing OR conditions in Where clause throws an exception

Fri, 13 May 2011 03:13:47 +0000

I have the next query:

        $qb =  $this->_em->createQueryBuilder();
    
          $qb ->select('Inventory')
            ->from('\Entity\Inventory', 'Inventory')
            ->leftJoin('Inventory.Variant', 'Variant')
            ->where('(Variant.isSellable = 0) OR (Variant IS NULL)')
           ->getQuery()->getResult();

that throws an exception:

 PHP Fatal error:  Call to undefined method Doctrine\ORM\Query\AST\ConditionalExpression::isSimpleConditionalExpression() .../Doctrine/ORM/Query/SqlWalker.php on line 1378.

The SqlWalker::walkConditionalPrimary function expects the $primary parameter passed to it to be an instance of Doctrine\ORM\Query\AST\ConditionalPrimary, but it is actually an instance of Doctrine\ORM\Query\AST\ConditionalExpression class that is passed in that case and of course it does not have a method called isSimpleConditionalExpression.

The workaround is to use extra parentheses around the conditions: ((Variant.isSellable = 0) OR (Variant IS NULL)) which does not seem to be very intuitive way.

[DDC-1148] [Patch] Auto infer parameter type in DQL

Fri, 13 May 2011 02:12:25 +0000

Here is the patch:

http://pastie.org/1891023
http://pastie.org/1891030

[DDC-170] Smarter IN() query mapping

Fri, 13 May 2011 02:11:56 +0000

This is my desired final product:

$users = $em->createQuery('SELECT FROM User u WHERE u.id IN :ids')
->setParameter('ids' => array(1, 2, 3))
->execute()

I am currently using unpleasant methods of generating strings of '?' to insert into the DQL, which is not quite as elegant as the rest of the DQL language.

[DDC-1147] Allow 0-based InputParameters in DQL

Wed, 11 May 2011 20:31:03 +0000

Currently it's impossible to define a 0-based input parameter.
This restriction of Doctrine 2 is odd, because we already have enough support to it, and restriction is merely cosmetic, and also prevents 1:1 array usage on DQL Parameters.

[DDC-1120] AbstractQuery::useResultCache no return type in phpdoc

Sun, 1 May 2011 06:17:33 +0000

@param string $resultCacheId
@return This query instance.
*/
public function useResultCache($bool, $timeToLive = null, $resultCacheId = null)
{

must be

@param string $resultCacheId
@return Doctrine\ORM\AbstractQuery This query instance.
*/
public function useResultCache($bool, $timeToLive = null, $resultCacheId = null)
{

[DDC-1043] Unit of Work - computeChangeSet

Sun, 1 May 2011 04:22:51 +0000

In the unit of work in the compute Change Set function. When comparing the old and the new value of a field. In the case 'Entity is "fully" MANAGED'. And the values are strings it is used

$orgValue != $actualValue

comparison operator instead of

$orgValue !== $actualValue

Which lead to not detecting some changes. I know it is not something major, but it is really annoying. So please fix it for the next release.

Thanks in advance.

[DDC-1094] Add Order and Limit to EntityRepository::findBy()

Sun, 1 May 2011 03:54:23 +0000

Currently repositories are pretty much useless because you cannot limit/offset or order by columns, which is what repositories are for to implement simple list views. That is why the signatures should be extended to:

findAll(array $orderBy = null, $maxResults = null, $firstResult = null);
findOne(array $criteria, array $orderBy = null, $maxResults = null, $firstResult = null);

[DDC-1133] DuckType AnnotationReader in AnnotationDriver

Sat, 30 Apr 2011 08:24:53 +0000

Currently the hint is strict in AnnotationDriver for the AnnotationReader. This should be duck-typed to support usage of https://github.com/schmittjoh/annotations

[DDC-1126] SchemaTool fails to dropSchema under SQLite due to ForeignKeyContraints checks

Tue, 26 Apr 2011 11:34:02 +0000

When attempting to $schemaTool->dropSchema($metadatas) using SQLite, it fails because it attempts to fetch for foreign key constraints.
Here is the exception:

PHP Fatal error:  Uncaught exception 'Doctrine\DBAL\DBALException' with message 'Operation 'Doctrine\DBAL\Platforms\AbstractPlatform::getListTableForeignKeysSQL' is not supported by platform.' in /Users/gblanco/Sites/mkx2/core/library/vendors/Doctrine/DBAL/DBALException.php:9
Stack trace:
#0 /Users/gblanco/Sites/mkx2/core/library/vendors/Doctrine/DBAL/Platforms/AbstractPlatform.php(1839): Doctrine\DBAL\DBALException::notSupported('Doctrine\DBAL\P...')
#1 /Users/gblanco/Sites/mkx2/core/library/vendors/Doctrine/DBAL/Schema/AbstractSchemaManager.php(261): Doctrine\DBAL\Platforms\AbstractPlatform->getListTableForeignKeysSQL('ProductEntity_P...', NULL)
#2 /Users/gblanco/Sites/mkx2/core/library/vendors/Doctrine/ORM/Tools/SchemaTool.php(639): Doctrine\DBAL\Schema\AbstractSchemaManager->listTableForeignKeys('ProductEntity_P...')
#3 /Users/gblanco/Sites/mkx2/core/library/vendors/Doctrine/ORM/Tools/SchemaTool.php(551): Doctrine\ORM\Tools\SchemaTool->getDropSchemaSQL(Array)
#4 /Users/gblanco/Sites/mkx2/core/tests/Tests/Database/AllTests. in /Users/gblanco/Sites/mkx2/core/library/vendors/Doctrine/DBAL/DBALException.php on line 9

[DDC-1125] Allow return data of Closure on EntityManager::transactional

Mon, 25 Apr 2011 17:33:42 +0000

Currently it is impossible to use transactional if you want to return an item from there.

This improvement would allow more flexible behavior from transactional.

[DDC-1012] Add isNull($param) and isNotNull($param) to querybuilder

Fri, 22 Apr 2011 02:44:11 +0000

Add isNull($param) and isNotNull($param) to querybuilder

[DDC-1110] CTI Entities always trigger ->find even when I'm calling ->getReference

Tue, 12 Apr 2011 05:19:01 +0000

Suppose we have some CTI mapped entities:

Group <- Company

Without having a given Entity on UnitOfWork IdentityMap, if I do:

$groupProxy = $em->getReference('Group', 1);

It will trigger the ->find (accessing the DB). This is correct on this situation, because the Entity can be either Group or Company. But if I do:

$companyProxy = $em->getReference('Company', 1);

There're no sub-classes anymore (Doctrine doesn't know it, but there are other ways to know), so it should correctly return an instance of CompanyProxy instead of trigger the ->find method.

The solution requires to build the hierarchy of Entities using their ClassMetadata. So it is require to loop though all mapped classes on DiscriminatorMap and check if there's 1 class that subclass the given Entity. If positive, return the result of ->find; otherwise a Proxy can be returned.
This is a non-optimal solution (a better solution would be to cache the hierarchy together with ClassMetadata), but it fixes the issue.

Issue could be considered as major since most CTI scenarios trigger unwanted DB queries, but its usage is so restrict that I left as minor.
We should fix that for 2.1 IMHO.

[DDC-991] Add method "getFirstResult()" that returns null on no result

Thu, 31 Mar 2011 17:42:31 +0000

There are some requests for a method on Query that return a first result or null.

[DDC-692] Read-only entities

Tue, 29 Mar 2011 14:18:15 +0000

It should be possible to mark an entity class as read-only so that it is never considered for change-tracking after it has been initially inserted into the database.

This feature is mainly a flush performance tweak to avoid checking objects for changes which can never actually change.

[DDC-696] Add onClear Event

Tue, 29 Mar 2011 13:44:25 +0000

There should be an event "onClear" that is called whenever someone calls "EntityManager::clear()".

This may be necessary in certain long-running script scenarios when you have additional identity maps / caching, for example based on unique fields of an entity.

[DDC-1014] Evaluate common date related functions for DQL inclusion

Sun, 27 Mar 2011 06:20:03 +0000

To check:

Difference in days between two dates
Add/subtract an interval to a date
Format a date
Return only Year, Month or Day, Day of Week, Week of Year of the date

[DDC-943] EntityRepository::findBy should support multiple values on criteria fetching

Wed, 16 Mar 2011 18:40:57 +0000

Currently it is impossible to execute a multiple value findBy on EntityRepository.

So supposing we have a Foo entity, we can do this:

$foos = $em->getRepository('Foo')->findByName('value');

But it is impossible to do:

$foos = $em->getRepository('Foo')->findByName(array('value1', 'value2'));

We have most of the support done inside BasicEntityPersister, but the _getSelectConditionSQL restricts to a single value by doing:

$conditionSql .= ' = ?'; at line 1150

We can extend the support easily by detecting array value and adding an IN (...) condition on this case.

[DDC-734] Possibility to fetch all outstanding proxies of an Entity

Wed, 16 Mar 2011 18:36:47 +0000

For performance reasons (solving the N+1 problem) it might be necessary to load all proxy instances of a given type:

$orders = $em->getRepository('Order')->findAll();
foreach ($orders AS $order) {
   $order->getCustomer()->getId(); // n+1
}

However say we could do something like:

$orders = $em->getRepository('Order')->findAll();
$em->getUnitOfWork()->loadProxies("Customer");

foreach ($orders AS $order) {
   $order->getCustomer()->getId(); // n+1
}

This doesnt make too much sense in this case because we could use a fetch join with DQL. However you easily get to the point where you have a query like:

SELECT b, e, r, p FROM Bug b JOIN b.engineer e 
JOIN b.reporter r JOIN b.products p ORDER BY b.created DESC

In this case the SQL generated is VERY huge and just the number of joins could cause an performance overhead. In general its better to keep the number of joins as small as possible, a solution here would optimize for the engineer and reporter being both instances of User:

$bugs = $em->createQuery("SELECT b, p FROM Bug b JOIN b.products p ORDER BY b.created DESC")->getResult();
$em->getUnitOfWork()->loadProxies("User"); // will load all engineers and reporters in one query

We could even make this nicer for using Queries:

$bugs = $em->createQuery("SELECT b, p FROM Bug b JOIN b.products p ORDER BY b.created DESC")
                        ->setQueryHint(Query::LOAD_PROXIES, array("User"))
                        ->getResult();

[DDC-865] Passing an array as parameter

Wed, 16 Mar 2011 18:35:26 +0000

First check the entites in attachments (I've deleted everything unnecessary for this example).

What I want to do is find multiple entities (I have their ids in array) and then do some action with each of them.

I'm trying to find those entites using IN operator in DQL query, but there is no way (or I was unable find it) to pass the array of ids as parameter to the query. I've tried several ways to do it (check the PictureRepository attachment) but none is working as i want. Further details are described in comments.

<?php
//I know i could use something like this but I wonder about the IN stetement right now. The example above is just for show.
foreach ($pictures as $value) {
$entity = $repository->find($value);
/...whatever i want to do with the $entity/
}
?>

[DDC-53] Introduce batching of eager loads

Wed, 16 Mar 2011 18:35:03 +0000

During hydration when an association is encountered that is configured EAGER this entity is directly loaded through a separate SQL statement. This is inefficient for single-valued associations as it leads to the n+1 queries problem. This should be improved by somehow collecting all entities that need to be eagerly fetched and loading them in a single statement or in batches.

[DDC-914] Use JOIN for Fetch=EAGER ManyToOne and OneToOne in Persisters

Wed, 16 Mar 2011 18:34:43 +0000

Currently Fetch=EAGER Only leads to proxies not being used, no optimizations are being done.

Optimizations could maybe be done easily for the cases:

1. Basic Entity Persister + ManyToOne
2. Basic Entity Persister + OneToOne + Owning side
3. Basic Entity Persister + OneToOne + Inverse side

Complicated cases would be:

Everything Single and JoinTableInheritance?
OneToMany and ManyToMany collections.

[DDC-963] @OneToOne inverse side executes queries even if object is in IdentityMap

Wed, 16 Mar 2011 18:34:28 +0000

@OneToOne inverse side executes queries even if object is in IdentityMap

[DDC-1060] Use Hydrators inside Persisters

Wed, 16 Mar 2011 18:34:11 +0000

The hydration code should be moved out of the persisters and re-using the Hydrators.

Reasons:

No duplication of hydration code necessary anymore.
More complex hydration (eager loads) possible inside persister

Implementation:

Either use a SimpleObjectHydrator or reuse the ObjectHydrator (benchmark)

Check for performance first.

[DDC-701] Code generation for DQL queries

Mon, 14 Mar 2011 00:09:34 +0000

It would be cool to have the possibility to define DQL queries in the mapping documents and let these be precompiled to SQL via a command-line code-generation target that produces for each DQL query the SQL and ResultSetMapping in native PHP code.

This allows people to work without a query cache and maximum performance, on the cost of another code-generation step.

There are already named queries currently but these must be defined in the Configuration at runtime and thus it does not bear any advantages.
I would propose removing this runtime named query facility and replacing it with a "compile-time" one. So that "named queries" are queries defined in the mapping, given a name, which can optionally be precompiled via the CLI. If not precompiled a named query should be handled like a normal query.

[DDC-1034] Registered lifecycle callbacks of derived classes have unexpected call sequence

Fri, 4 Mar 2011 17:04:55 +0000

Situation:
Create an abstract base class (@InheritanceType("JOINED")) and a derived class, both having the annotation @HasLifecycleCallbacks and both having a method with annotation @PostLoad (different method names). The sequence of methods being called when an object is loaded from the database is not as expected.

Expected output:
Called Che\Tmp\BaseClass::PostLoadBase
Called Che\Tmp\DerivedClass::PostLoadDerived
(base value, derived value)

Actual output:
Called Che\Tmp\BaseClass::PostLoadBase
Called Che\Tmp\DerivedClass::PostLoadDerived
Called Che\Tmp\BaseClass::PostLoadBase
(base value)

Test code:
See attachment for classes

// Assume there is an entity manager $em
// Create object
$newDerived = new \Che\Tmp\DerivedClass();
$em->persist($newDerived);

// Fetch object
$derived = $em->findById('\Che\Tmp\DerivedClass', 1);
$derived->echoList();

Possible problem cause

ClassMetadataInfo::addLifecycleCallback($callback, $event) method has a note 'If the same callback is registered more than once, the old one will be overridden'. We are not sure whether this is the case.

[DDC-1056] Using the StaticPHPDriver throws PHP Error Undefined property: Doctrine\ORM\Mapping\Driver\StaticPHPDriver::$_classNames

Fri, 4 Mar 2011 16:23:55 +0000

Using the StaticPHPDriver throws PHP Error Undefined property: Doctrine\ORM\Mapping\Driver\StaticPHPDriver::$_classNames

this is due to the class not having the two required instance variables $this->_classNames and $this->_fileExtension.

[DDC-1041] UnitOfWork tryGetById method is always called with the rootEntityName

Fri, 4 Mar 2011 15:56:45 +0000

My problem : i have a class table inheritance, with only 3 class, one abstract and two concrete.
says AbstractClass, ConcretClassA and ConcreteClassB
All three are declared with @entity

if i already have in my identity map the ConcretClassA with id = 1
when i do an entityManager->find('ConcreteClassB', 1) the identityMap returns me the ConcretClassA with id = 1
that's not correct !
it should return a null value instead

That's because the entityRepository (and all the other doctrine class) call the UnitOfWork tryGetById with the rootEntityName, which in my case is AbstractClass.
See the first line of the entityRepository's find method :

$this->_em->getUnitOfWork()->tryGetById($id, $this->_class->rootEntityName)

if i change this line to :

$this->_em->getUnitOfWork()->tryGetById($id, $this->_class->name)

the find method return the expected null value.

So, why the UnitOfWork tryGetById method is always called with the rootEntityName ?

[DDC-1036] the Aggregate Expressions "AVG" | "MAX" | "MIN" | "SUM", should be followed by SimpleArithmeticExpression

Sun, 20 Feb 2011 03:16:19 +0000

the Aggregate Expressions "AVG" | "MAX" | "MIN" | "SUM", should be not only followed by StateFieldPathExpression , but also SimpleArithmeticExpression,
see http://www.doctrine-project.org/docs/orm/2.0/en/reference/dql-doctrine-query-language.html#aggregate-expressions

i found it can not execute dql like
select sum(c.quantity * c.price) total_price from cart c

i think, this should be a bug

[DDC-982] Make SQLWalker::getSQLTableAlias() more unique with dql aliases

Sun, 20 Feb 2011 03:00:48 +0000

getSqlTableAlias: $tableName .= $dqlAlias;

say there is a guy who has two tables "user" and "users" and he does SELECT * FROM User s

[DDC-953] CLI tools orm:generate-entities --regenerate-entities=1 flag will generate empty entities 50% of time.

Tue, 8 Feb 2011 09:20:25 +0000

Running the command:
doctrine orm:generate-entities --regenerate-entities=1 --generate-annotations=1 ./

50% of the time my entity will appear as:
<?php

namespace models;

/**

models\Role
*
@Table(name="roles")
@Entity(repositoryClass="models\repositories\RoleRepository")
*/
class Role
{

}

The other 50% everything will be in there. In addition, if the --regenerate-entities=1 argument is removed, if I change the data in my YAML schema file for a column (such as changing length=255 to length=50 on a string), the annotations won't be updated when the updated entity is generated. It seems only new fields are being added to the entity files which is why --regenerate-entities=1 was required in the first place.

[DDC-1018] INDEX BY does not work in JOIN clauses

Dependency — Sat, 5 Feb 2011 04:34:15 +0000

It seems INDEX BY only works in the FROM, not in JOIN clauses.

This is a dependency for ~~DDC-250~~

[DDC-1006] Entity Generator Regenerate If Not New

Wed, 2 Feb 2011 17:33:01 +0000

When regenerating entities from xml ( and i am sure all others ) it gives a blank entity class when the file exists and the regenerateIfExists is set to true, the expected result would be a full entity with any removed columns removed from the entity and new columns to be added.

i've come up with a fix that i assume is the correct way
i haven't tested this without the regeneration set to true since my application requires the regeneration, here's my code block i'm using:

$em->getConfiguration()->setMetadataDriverImpl(
new \Doctrine\ORM\Mapping\Driver\SesXmlDriver(
'ext/Doctrine/Entities/xml_metadata/'
)
);

$cmf = new Doctrine\ORM\Tools\DisconnectedClassMetadataFactory();
$cmf->setEntityManager($em);
$metadata = $cmf->getAllMetadata();

$generator = new \Doctrine\ORM\Tools\EntityGenerator();
$generator->setGenerateAnnotations(true);
$generator->setGenerateStubMethods(true);
$generator->setRegenerateEntityIfExists(true);
//$generator->setUpdateEntityIfExists(true);
$generator->generate($metadata, 'ext/');

in the _hasProperty and _hasMethod functions, need to add the below to the inline check:

( ! $this->_isNew && $this->_regenerateEntityIfExists)

[DDC-1002] bug in generate entities with many2many relationships from xml/yml shcemes

Wed, 2 Feb 2011 17:32:38 +0000

I try use many2many relations in my symfony2 learning project https://github.com/symfony/symfony.git
But entities thar generates from yml schemes did not meet entities from doctrine2 guide or entities from beberlei Whitewashing project https://github.com/beberlei/Whitewashing/tree/master/Blog

After that I try generate similar entitries is doctrine2-sandbox. Problem is the same
I attached yml schemes and result entities.

Problem:

Entities\Address does not have relations with Entities\User
In Entities\User property $adresses instance of Entity\Address. But this Doctrine\Common\Collections\ArrayCollection or no?
```
    /**
     * @var Entity\Address
     */
    private $addresses;
```

In Entities\User not at __constructor() method:

    public function __construct()
    {
        $this->addresses = new ArrayCollection();
    }

[DDC-1008] Entity Generator Stub Method For Id Generator

Wed, 2 Feb 2011 17:32:07 +0000

In the EntityGenerator when the id setting has a generator of NONE it does not add the stub method for setting the id keys value, here's my fix:

around line 478 in the _generateEntityStubMethods function, the first foreach which checks for the id mapping, change:

if ( ! isset($fieldMapping['id']) || ! $fieldMapping['id']) {

if ( ! isset($fieldMapping['id']) || ! $fieldMapping['id'] || ($this->_getIdGeneratorTypeString($metadata->generatorType) == 'NONE')) {

[DDC-892] Caches can potentially return false positives due to use of MD5 hash codes as keys. A classic.

Sun, 23 Jan 2011 14:55:26 +0000

I was just checking the execution path for efficiency and bumped into this block of code in /Doctrine/ORM/AbstracQuery.php,
starting on line 560:

protected function _getResultCacheId()
{
if ($this->_resultCacheId)

{ return $this->_resultCacheId; }

else

{ $sql = $this->getSql(); ksort($this->_hints); return md5(implode(";", (array)$sql) . var_export($this->_params, true) . var_export($this->_hints, true)."&hydrationMode=".$this->_hydrationMode); }

}

Of course, MD5 hashes can never be guaranteed to be unique, so this block of the doExecute-Method
starting on line 508 can return false positives and thus break the user's assumptions about the ORM's behavior:

// Check result cache
if ($this->_useResultCache && $cacheDriver = $this->getResultCacheDriver()) {
$id = $this->_getResultCacheId();
$cached = $this->_expireResultCache ? false : $cacheDriver->fetch($id);

if ($cached === false)

{ // Cache miss. $stmt = $this->_doExecute(); $result = $this->_em->getHydrator($this->_hydrationMode)->hydrateAll( $stmt, $this->_resultSetMapping, $this->_hints ); $cacheDriver->save($id, $result, $this->_resultCacheTTL); return $result; }

else

{ // Cache hit. return $cached; }

}

It is not likely to happen, but possible. Rely on it a couple of million times in a production system, and one day, eventually, it will fail
and hell will break loose.

I think it is prohibitive to try to save memory by giving up correctness. If your program does not work, it's simply broken and there is no need to tune it unless you fix it functionally.

The only safe solution would be to use a non-lossy hash (i. e. compression) method, if any. Plain query text would do fine too.

Unless you expect the user to anticipate false positives, i. e.

[DDC-958] postLoad event triggering

Sun, 23 Jan 2011 11:28:36 +0000

Currently I've noticed that postLoad event is not triggered on $em->refresh($entity); it seems like entity should be reloaded on this call
and logically postLoad event should be also triggered if entity is being reloaded.

[DDC-968] Query hints should be retrievable by user

Sun, 23 Jan 2011 10:48:26 +0000

Currently the only way to set additional parameters accessible by AST TreeWalker is using the query hints.
the main problem is then query is being cloned, hints are flushed and the only way to set them is to access them by name and feed to cloned query one by one.
I think there should be Query::getHints() method available to the userland

[DDC-997] Call to undefined method isIdentifier in AbstractHydrator.php line 197

Sun, 23 Jan 2011 10:42:21 +0000

Call to undefined method isIdentifier in AbstractHydrator.php line 197

[DDC-969] SchemaTool fails with class table inheritance if id columnName is not "id"

Sun, 23 Jan 2011 10:13:31 +0000

In method getSchemaFromMetadata() within the $class->isInheritanceTypeJoined() part the following line

Doctrine\ORM\Tools\SchemaTool::getSchemaFromMetadata() — Line 182

$table->getColumn($class->identifier[0])->setAutoincrement(false);

leads to a Doctrine\DBAL\Schema\SchemaException::columnDoesNotExist() if a columnName other then id is used for the id field, as not the columnName (but the field name) is passed to $table->getColumn().

Should rather be

$table->getColumn($columnName)->setAutoincrement(false);

[DDC-978] Many-To-Many relations are removed after Flush()

Duplicate — Sun, 23 Jan 2011 09:41:26 +0000

Let's say we have three entities: User, Channel, and Log

Every time a User is created or updated, Channels are assigned to a Many-To-Many collection.
This action gets logged in the Log entity.

I have reproduced the bug in the Doctrine sandbox (see attachment). It's a fully working example.
This is a summary:

This works

// Fetch two channels in an array
$channels = .......

// create a new user and assign channels
$user = new User();
$user->setName('FooBar');
$user->setChannels($channels);

//save the user
$em->persist($user);
$em->flush();

// log it
$log = new Log();
$log->setMessage('User created with two channels');
$log->setItem($user);

$em->persist($log);
$em->flush();

This also works

// Fetch two channels in an array
$channels = .......

// fetch an existing user, *change something to the user*, and assign channels
$user = .............
$user->setName('Gaz');
$user->setChannels($channels);

//save the user
$em->persist($user);
$em->flush();

// log it
$log = new Log();
$log->setMessage('User created with two channels');
$log->setItem($user);

$em->persist($log);
$em->flush();

This does not work (channels are removed)

// Fetch two channels in an array
$channels = .......

// fetch an existing user and only assign channels, change nothing else
$user = .............
$user->setChannels($channels);

//save the user
$em->persist($user);
$em->flush();

// log it
$log = new Log();
$log->setMessage('User created with two channels');
$log->setItem($user);

$em->persist($log);
$em->flush();

This last piece of code generates following SQL code (summarized):

DELETE FROM user_channels WHERE userId = 1
INSERT INTO user_channels (userId, channelId) VALUES (1, 2);
DELETE FROM user_channels WHERE userId = 1

If you remove the $em->flush() after $em->persist($user); in the last example, the code works (channels are persisted).

I did not have this problem with Doctrine2 Alpha4.

[DDC-996] Empty field names lead to weird exception

Sun, 23 Jan 2011 08:23:53 +0000

Empty field names (possible in xml and yml) lead to weird exception messages, they should throw a MappingException::missingFieldName exception.

[DDC-960] Locking @Version with MappedSuperClass and Single Table Inheritance results in wrong queries

Sun, 23 Jan 2011 07:00:53 +0000

When using a @version field for locking purposes in one of the fields of a MappedSuperClass, things go wrong. Here is my situation:

SpecificUser extends of BaseUser
There is one mapped superclass containing things like createdOn, createdBy and finally the @version field named version.

Now, when I change a record, the following queries are created. The last one is faulty:

Query: UPDATE specificuser SET firstname = ? WHERE id = ?
Query: UPDATE baseuser SET version = version + 1 WHERE id = ? AND version = ?
Query: SELECT version FROM specificuser WHERE id = ? <======= should be: SELECT version FROM baseuser WHERE id = ?

[DDC-942] Query getSingleResult throws inappropiate exceptions.

Tue, 18 Jan 2011 15:27:31 +0000

Currently when using the Query object or QueryBuilder there is no easy way to get the first found result with doing a lot of work. The method that seems to be for this purpose is getSingleResult but it throws an exception if no records are found and if there is more than one record found another Exception is thrown. This behavior is different than the ODM\MongoDB where null is returned.

[DDC-980] SQL alias behavior inconsistent in UPDATE ... WHERE (subselect)

Thu, 13 Jan 2011 15:19:26 +0000

When using a DQL UPDATE with a subselect in the WHERE clause (such as what the size() function generates), the subselect is trying to reference an alias that is not defined in the main UPDATE clause. Using the size() function similarly in a SELECT statement works fine, the problem is only occurring for me when I try an UPDATE. I have not tried it with INSERT or DELETE, but I would suspect a similar inconsistency with anything other than the more common usage with SELECT.

$q = $em->createQuery('UPDATE Event e SET e.no_speakers = 1, e.no_credits = 1 WHERE size(e.Instances) = 0');
print $q->getSQL();

Output:

UPDATE Event SET no_speakers = 1, no_credits = 1 WHERE (SELECT COUNT(*) FROM Instance c0_ WHERE c0_.Event_id = c1_.id) = 0

And, $q->execute() results in:

PHP Fatal error:  Uncaught exception 'PDOException' with message 'SQLSTATE[42S22]: Column not found: 1054 Unknown column 'c1_.id' in 'where clause'' in /var/www/v3-lf/library/Doctrine/DBAL/Connection.php:657
Stack trace: #0 /var/www/v3-lf/library/Doctrine/DBAL/Connection.php(657): PDO->exec('UPDATE Event...')

[DDC-117] Allow @Id on @ManyToOne fields

Duplicate — Sun, 9 Jan 2011 15:10:40 +0000

Sometimes, a @ManyToOne field has to be the Primary Key, or part of the Primary Key. Adding @Id to the @ManyToOne does not help, an additional property with duplicates the referenced id is needed:

(userId and User field in the Phonenumber class - to be able to set @Id on userId):
http://pastebin.com/d51e021e2

Allowing @Id on @ManyToOne fields (which would make the JoinColumn a PK) would help here. Any maybe this would also fix ~~DDC-116~~

[DDC-546] New fetch mode EXTRA_LAZY for collections

Reference — Sun, 2 Jan 2011 09:16:27 +0000

A new fetch mode EXTRA_LAZY for one-to-many and many-to-many associations could have the following effects on PersistentCollection methods:

count() : Does not initialize the collection but issues a straight SQL count query.
remove($key) : Does not initialize the collection but issues straight SQL instead.
removeElement($element) : Does not initialize the collection but issues straight SQL instead.
contains($element) : Does not initialize the collection but issues straight SQL instead.
containsKey($key) : Does not initialize the collection but issues straight SQL instead.

This mode would usually be useful for (potentially) large collections.

We need to work out concrete use-case examples and implementation proposals before implementation.

The semantics of the mentioned methods with EXTRA_LAZY need to be carefully worked out, i.e. what happens to already managed instances in case of the remove operations and stuff like that.

[DDC-949] strange behavior with boolean types when using findOneBy() in a CLI phpunit test

Sun, 2 Jan 2011 07:14:01 +0000

I do not see this behavior when running findByOne() calls via the Apache SAPI. No clue really what could possibly cause this. Not sure how to get the error logger to output something in a phpunit test (never really figured out how phpunit supports debugging). Essentially if I run the tests with SQLite the case with 'false' fails and when I run with PostgreSQL the case with 0 fails. Essentially in the fail case I get an instance of $this, just like when I pass: false.

Tell me if this report is useless in the current state and then I will work on separating it out into a standalone CLI script without Symfony2 and phpunit. But I dont want to spend more time on this if it isnt necessary.

[DDC-922] Persisting an entity with an 1:n collection of related entites fails if the FK ist part of a composite PK

Sun, 2 Jan 2011 06:05:33 +0000

If you got two Entities A and B where A is a sample Entity with a 1:n relation to the Entity B
and B has a composite PK with the FK (A id) and a custom field like this:

EntityA:
  type: entity
  table: entity_a
  repositoryClass: EntityARepository
  id:
    id:
      type: integer
      generator:
        strategy: AUTO
  fields:
    handle:
      type: string
      length: 32
      unique: true
 oneToMany:
    entites_b:
      targetEntity: EntityB
      mappedBy: entity_a
      cascade: [persist]

EntityB:
  type: entity
  table: entity_b
  repositoryClass: EntityBRepository
  id:
    description:
      type: string
      length: 255
      notnull: true
      generator:
        strategy: NONE
    entitiy_a_id:
      type: integer
      length: 11
      notnull: true
      generator:
        strategy: NONE
  fields:
    value:
      type: string
      length: 255
  manyToOne:
    entitiy_a:
      targetEntity: EntitiyA
      inversedBy: entities_b

Class EntityA
{
    private $id;
    
    private $handle;
    
    private $b_coll;
    
    public function addB(EntityB $ent) 
    {
        $this->b_coll->add($ent);
        $b->setA($this);
    }
}

Class EntityB
{
    private $description;
    private $entity_a_id;
    
    private $value;
    
    private $entity_a;
    
    public function setA(EntityA $ent)
    {
        $this->entity_a = $ent;
    }
}

If you try to persist an object of A holding one or more references to objects of B, the objects get correctly persistet. This means, that every inserted record of B has a correctly filled field "entity_a_id". The objects of B also have a correct reference to A holding now the new A record with its autoinc id.
But the object property "entity_a_id" stays empty. This leads to a collection of unusable EntityB objects (in memory), since on another persist of EntityA the values of entity_a_id are still not set correctly but the state is managed which leads to an "update B ... where entity_a_id=0"
We've tried to set the entity_a_id with an event handler on postPersist. On a persist of EntityA the collection entities wanted to update their entity_a_ids from 0 to the correct one.

[DDC-881] DDC-117: Linked Objects with composite key

Sun, 2 Jan 2011 06:05:12 +0000

I'm currently playing around with ~~DDC-117~~. I came across a general
problem which occurs with relations.

Given the following two classes, should a
@OneToOne/@OneToMany/@ManyToMany relation consider a composite ID or is
that not planned with ~~DDC-117~~?

In the past, we assumed that an object is identified unique with an @Id
column. However, if we support composite keys, an object needs to be
identified by two or more columns, which we need to take into
consideration when building queries and foreign keys. Is that correct?

/**
 * @Entity
 */

class Document {
	/**
	 * @Id
	 * @Column(type="integer")
	 * @GeneratedValue(strategy="AUTO")
	 */
	private $id;

	/**
	 * @Id
	 * @Column(type="integer")
	 */
	private $version;

	/**
	 * @ManyToOne(targetEntity="Content")
	 * Enter description here ...
	 * @var unknown_type
	 */
	private $content;
}

/**
 * @Entity
 */
class Content {
	/**
	 * @Id
	 * @Column(type="integer")
	 * @GeneratedValue(strategy="AUTO")
	 */
	private $id;

	/**
	 * @Id
	 * @Column(type="integer")
	 */
	private $version;

	/**
	 * @ManyToOne(targetEntity="Document")
	 */

	private $document;
}

I know this might become a bit tricky, because $content refers to a
single instance of Content, but we actually need two columns to identify
it. That's how it looks if generated with Doctrine2 (~~DDC-117~~):

mysql> describe Document;
+------------+---------+------+-----+---------+-------+
| Field      | Type    | Null | Key | Default | Extra |
+------------+---------+------+-----+---------+-------+
| id         | int(11) | NO   | PRI | NULL    |       |
| version    | int(11) | NO   | PRI | NULL    |       |
| content_id | int(11) | YES  | MUL | NULL    |       |
+------------+---------+------+-----+---------+-------+

mysql> describe Content;
+-------------+---------+------+-----+---------+-------+
| Field       | Type    | Null | Key | Default | Extra |
+-------------+---------+------+-----+---------+-------+
| id          | int(11) | NO   | PRI | NULL    |       |
| version     | int(11) | NO   | PRI | NULL    |       |
| document_id | int(11) | YES  | MUL | NULL    |       |
+-------------+---------+------+-----+---------+-------+

However, to make my example work, the tables would need to look the
following:

mysql> describe Content;
+------------------+---------+------+-----+---------+-------+
| Field            | Type    | Null | Key | Default | Extra |
+------------------+---------+------+-----+---------+-------+
| id               | int(11) | NO   | PRI | NULL    |       |
| version          | int(11) | NO   | PRI | NULL    |       |
| document_id      | int(11) | YES  | MUL | NULL    |       |
| document_version | int(11) | YES  |     | NULL    |       |
+------------------+---------+------+-----+---------+-------+

mysql> describe Document;
+-----------------+---------+------+-----+---------+-------+
| Field           | Type    | Null | Key | Default | Extra |
+-----------------+---------+------+-----+---------+-------+
| id              | int(11) | NO   | PRI | NULL    |       |
| version         | int(11) | NO   | PRI | NULL    |       |
| content_id      | int(11) | YES  | MUL | NULL    |       |
| content_version | int(11) | YES  |     | NULL    |       |
+-----------------+---------+------+-----+---------+-------+

It would be nice if we could discuss this one, as I feel it is important for an ORM.

[DDC-966] SchemaTool does not check for inherited fields in STI sub-classes and overwrites their column definitions to DEFAULT NULL

Sun, 2 Jan 2011 05:52:25 +0000

Example

/**
 * @Entity
 * @Table(
 *     name="eav_attribute",
 *     uniqueConstraints={
 *         @UniqueConstraint(columns={"core_project_id", "name"})
 *     }
 * )
 * @InheritanceType(
 *     "SINGLE_TABLE"
 * )
 * @DiscriminatorColumn(
 *     name="datatype",
 *     type="string"
 * )
 * @DiscriminatorMap({
 *     "datetime"="AttributeDatetime",
 *     "decimal"="AttributeDecimal",
 *     "int"="AttributeInt",
 *     "string"="AttributeString",
 *     "text"="AttributeText"
 * })
 */
abstract class AbstractAttribute
{
    // ...
    
    /**
     * @Column(type="string")
     */
    protected $name;

    /**
     * @Column(type="boolean")
     */
    protected $is_unique;

    // ...
}

/**
 * @Entity
 */
class AttributeDatetime extends AbstractAttribute
{
}

Expected SQL-dump:

name VARCHAR(255) NOT NULL,
is_unique TINYINT(1) NOT NULL,

SQL-dump created by SchemaTool:

name VARCHAR(255) DEFAULT NULL,
is_unique TINYINT(1) DEFAULT NULL,

This behaviour is problematic, especially for columns which are part of a unique constraint.

Reason:

SchemaTool doesn't really check for inherited fields in STI sub classes in method getSchemaFromMetadata() and passes all fields (incl. the inherited) to method _gatherColumn() where finally the column definition of the parent class will be overwritten.

Doctrine\ORM\Tools\SchemaTool

private function _gatherColumn($class, array $mapping, $table)
{
    // Lines 309 - 311
    if ($class->isInheritanceTypeSingleTable() && count($class->parentClasses) > 0) {
        $options['notnull'] = false;
    }
}

A quick fix:

Change that if-clause above to

if ($class->isInheritanceTypeSingleTable() && count($class->parentClasses) > 0 && ! isset($mapping['inherited'])) {

Better fix:

Only pass not inherited fields to the _gatherColumn() method, as done with CTI sub classes.

[DDC-965] Check for ID in CMF should be done after Event invocation

Sun, 2 Jan 2011 04:25:57 +0000

Check for ID in CMF should be done after Event invocation

[DDC-955] PostgresSQL + No identifier / primary key for Specified Entity 'Table'. Every Entity must have for an identifier / primary key.

Thu, 30 Dec 2010 17:20:57 +0000

PostgreSQL error map from reverse engineering is not recognized by the primary keys in PostgreSQL and throws the following error: "No identifier / primary key for Specified Entity 'Table'. Every Entity must have for an identifier / primary key."

[DDC-874] orm:convert-mapping

Thu, 30 Dec 2010 17:20:15 +0000

I have a Postgres SQL database.
The Base has only one table "User" with two attributes (name and id).
"Id" is primary key.

The failure to execute the task:
php orm doctrine: convert-mapping - from-database yml / home / cristian / database.yml

is:

[Doctrine \ ORM \ Mapping \ MappingException]
No identifier / primary key for Specified Entity 'User'. Every Entity must have for an identifier / primary key

Script to create the table:

CREATE TABLE "User"
(
id serial NOT NULL,
name character varying (55),
CONSTRAINT "User_pkey" PRIMARY KEY (id)
)
WITH (
OIDS = FALSE
)
ALTER TABLE "User" OWNER TO postgres;

[DDC-929] A index has to be named as "primary" to be detected Doctrine\ORM\Mapping\Driver\DatabaseDriver::loadMetadataForClass()

Thu, 30 Dec 2010 17:19:55 +0000

Condition

if (isset($indexes['primary']) && in_array($column->getName(), $indexes['primary']->getColumns())) {

needs the primary key to be named as primary. Discovered this when reverse engineering an existing database.

Fix, that worked for me:

Replace:

if (isset($indexes['primary']) && in_array($column->getName(), $indexes['primary']->getColumns())) {
$fieldMapping['id'] = true;

With:

$primary = false;

foreach ($indexes as $index)
{
if ($index->isPrimary())
{
if (in_array($column->getName(), $index->getColumns()))

{ $primary = true; break; }

}
}

if ($primary){
$fieldMapping['id'] = true;

[DDC-961] First letters are missing in M:N tables

Thu, 30 Dec 2010 16:32:42 +0000

When I define M:N relation and update the schema by SchemaTool then the joining table is created without first letters (e.g. rticle_ag instead of article_tag). Relevant part from the source code:

<?php
/** @entity */
class Article {
	/** @manyToMany(targetEntity="Tag") */
	public $tags;
}

/** @entity */
class Tag {
	/** @manyToMany(targetEntity="Article", mappedBy="tags") */
	public $articles;
}

$tool = new \Doctrine\ORM\Tools\SchemaTool($em);
$tool->updateSchema(array(
	$em->getClassMetadata('Article'),
	$em->getClassMetadata('Tag'),
));
?>

You can download the complete example at http://www.notorm.com/static/doctrine2-notorm/

[DDC-795] Wrong SQL statement when using loadOneToManyCollection

Duplicate — Tue, 28 Dec 2010 13:06:22 +0000

I have the following SQL

CREATE TABLE `article` (
  `articleID` int(11) NOT NULL AUTO_INCREMENT,
  `reference` varchar(255) DEFAULT NULL,
  `addDt` datetime DEFAULT NULL,
  PRIMARY KEY (`articleID`)
) ENGINE=InnoDB AUTO_INCREMENT=1 DEFAULT CHARSET=utf8;


CREATE TABLE `articleRelated` (
  `articleID` int(11) NOT NULL,
  `relatedArticleID` int(11) NOT NULL,
  PRIMARY KEY (`articleID`,`relatedArticleID`),
  KEY `a1` (`articleID`),
  KEY `a2` (`relatedArticleID`),
  CONSTRAINT `a1` FOREIGN KEY (`articleID`) REFERENCES `article` (`articleID`) ON DELETE NO ACTION ON UPDATE NO ACTION,
  CONSTRAINT `a2` FOREIGN KEY (`relatedArticleID`) REFERENCES `article` (`articleID`) ON DELETE NO ACTION ON UPDATE NO ACTION
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

And these 2 models

Article.php

<?php
/**
 * Model for article
 * 
 * @Table(name="article") 
 * @Entity
 */
class App_Model_Article
{

    /**
     * @var integer articleID
     * @Column(name="articleID", type="integer", nullable=false) 
     * @GeneratedValue(strategy="IDENTITY") 
     * @Id
     */
    protected $_articleID = null;

    /**
     * @var string reference
     * @Column(name="reference", type="string", nullable=true, length=255)
     */
    protected $_reference = null;

    /**
     * @var datetime addDt
     * @Column(name="addDt", type="datetime", nullable=true)
     */
    protected $_addDt = null;

    /**
     * @OneToMany(targetEntity="App_Model_ArticleRelated", mappedBy="_article", cascade={"persist"})
     */
    protected $_articleRelatedRefArticle = array();

    /**
     * @OneToMany(targetEntity="App_Model_ArticleRelated", mappedBy="_relatedArticle", cascade={"persist"})
     */
    protected $_articleRelatedRefRelatedArticle = array();
}

and

ArticleRelated.php

<?php

/**
 * Model for articleRelated
 * 
 * @Table(name="articleRelated") 
 * @Entity
 */
class App_Model_ArticleRelated
{

    /**
     * @ManyToOne(targetEntity="App_Model_Article") 
     * @JoinColumn(name="articleID", referencedColumnName="articleID") 
     * @Id
     */
    protected $_article = null;

    /**
     * @ManyToOne(targetEntity="App_Model_Article") 
     * @JoinColumn(name="relatedArticleID", referencedColumnName="articleID") 
     * @Id
     */
    protected $_relatedArticle = null;
}

When I do the following

$firstArticle = $this->_entityManager->find('App_Model_Article', 54);
      
$related = $firstArticle->getArticleRelated('article');
foreach ($related as $art) {
       	var_dump($art);
}

it generates the following SQL

SELECT , t1.articleID AS articleID0, t1.relatedArticleID AS relatedArticleID2 FROM articleRelated t1 WHERE articleID = ?

I tracked the problem down to the following method

Doctrine/ORM/Persisters/BasicEntityPersister.php

//...
protected function _getSelectColumnListSQL()
    {
        if ($this->_selectColumnListSql !== null) {
            return $this->_selectColumnListSql;
        }

        $columnList = '';

        // Add regular columns to select list
        foreach ($this->_class->fieldNames as $field) {
            if ($columnList) $columnList .= ', ';
            $columnList .= $this->_getSelectColumnSQL($field, $this->_class);
        }

        $this->_selectColumnListSql = $columnList . $this->_getSelectJoinColumnsSQL($this->_class);
		
        return $this->_selectColumnListSql;
    }
//....

Because $this->_class->fieldNames is empty for my class, $columnList will also be empty.
$this->_getSelectJoinColumnsSQL($this->_class) generates
", t1.articleID AS articleID0, t1.relatedArticleID AS relatedArticleID2"
so $this->_selectColumnListSql == ", t1.articleID AS articleID0, t1.relatedArticleID AS relatedArticleID2"

I fixed the problem by adding trim:

$this->_selectColumnListSql = trim($columnList . $this->_getSelectJoinColumnsSQL($this->_class), ',');

[DDC-837] Two children in inheritance with same property name causes error in hydration

Tue, 28 Dec 2010 08:59:35 +0000

This is related to ~~DDC-258~~. The issue seems to be fixed with regular column types (string, int, etc) but the same issue has cropped up when we have a OneToOne relationship in two child classes that share the same property name. I have modified the DDC258TestCase class to demonstrate the error.

To summarize: two classes that inherit from the same class happen to have a property with the same name. Both of them are oneToOne relationships. Querying for the objects, one object type (depending on discriminatorMap order) will be hydrate correctly but the other will always be null.

[DDC-928] Using uninitialised variable in lib/Doctrine/ORM/Tools/ConvertDoctrine1Schema.php

Tue, 28 Dec 2010 06:20:48 +0000

A call:

$metadata->setSequenceGeneratorDefinition($definition);

is performed a line above the definition of the $definition variable.

Fix: Switch those two lines:

// $metadata->setSequenceGeneratorDefinition($definition); //was here
$definition = array(
'sequenceName' => is_array($column['sequence']) ? $column['sequence']['name']:$column['sequence']
);
$metadata->setSequenceGeneratorDefinition($definition); //belongs here

On line 191 in RC2 release.

[DDC-617] ObjectHydrator issue with OneToMany relationship

Tue, 28 Dec 2010 04:25:07 +0000

I'm pretty new to this ORM thing but I am having a weird issue with a DQL query I think should work (or throw an exception). I have the following code:

namespace Lms\Entities;
/**
 *
 * @Entity
 * @Table(name="User")
 */
class User {

	public function __constructor() {
		$social_media_links = new \Doctrine\Common\Collections\ArrayCollection;
	}
	/**
	 * @Id
	 * @Column(type="bigint")
	 * @GeneratedValue
	 */
	protected $id;

	/** @Column(type="string", nullable=TRUE, length=1024) */
	protected $mission_statement;

	/** @Column(type="string") */
	protected $first_name;

	/** @Column(type="string") */
	protected $last_name;

	/** @Column(type="string", nullable=TRUE, length=8) */
	protected $initial;

	/** @Column(type="string", nullable=TRUE) */
	protected $email;

	/** @Column(type="string", nullable=TRUE) */
	protected $company;

	/** @Column(type="string", nullable=TRUE, length=1024) */
	protected $picture;

	/** @Column(type="text", nullable=TRUE) */
	protected $bio;

	// unidirectional one to many relationship with social media link
	/**
	 * @ManyToMany(targetEntity="SocialMediaLink")
	 * @JoinTable(name="Users_Socialmedialinks",
	 *      joinColumns={@JoinColumn(name="user_id", referencedColumnName="id")},
	 *      inverseJoinColumns={@JoinColumn(name="socialmedialink_id", referencedColumnName="id", unique=true)}
	 *      )
	 */
	protected $social_media_links;
	

    /**
     * Add social_media_links
     *
     * @param SocialMediaLink $socialMediaLinks
     */
    public function addSocialMediaLinks(\SocialMediaLink $socialMediaLinks)
    {
        $this->social_media_links[] = $socialMediaLinks;
    }

    /**
     * Get social_media_links
     *
     * @return Doctrine\Common\Collections\Collection $socialMediaLinks
     */
    public function getSocialMediaLinks()
    {
        return $this->social_media_links;
    }
}

namespace Lms\Entities;

/**
 *
 * @Entity
 * @Table(name="SocialMediaLink")
 */
class SocialMediaLink {

	/**
	 * @Id
	 * @Column(type="bigint")
	 * @GeneratedValue
	 */
	protected $id;

	/** @Column(type="string") */
	protected $title;

	/** @Column(type="string") */
	protected $link;

}

And when I execute:

		$sml = $this->_em->createQuery("SELECT s FROM Lms\Entities\User u JOIN u.social_media_links  AS s WHERE u.id = ?1 AND s.id = ?2")
					->setParameter(1, 1)
					->setParameter(2, 1)
					->getResult();

I get the following trace:

1) DoctrineExtensions\PHPUnit\UserTestCase::testEditSocialMediaLink
class_parents(): object or string expected

C:\xampp\htdocs\lms-user-sml-feature\system\application\libraries\Doctrine\ORM\Mapping\ClassMetadataFactory.php:201
C:\xampp\htdocs\lms-user-sml-feature\system\application\libraries\Doctrine\ORM\Mapping\ClassMetadataFactory.php:224
C:\xampp\htdocs\lms-user-sml-feature\system\application\libraries\Doctrine\ORM\Mapping\ClassMetadataFactory.php:148
C:\xampp\htdocs\lms-user-sml-feature\system\application\libraries\Doctrine\ORM\EntityManager.php:235
C:\xampp\htdocs\lms-user-sml-feature\system\application\libraries\Doctrine\ORM\Internal\Hydration\ObjectHydrator.php:220
C:\xampp\htdocs\lms-user-sml-feature\system\application\libraries\Doctrine\ORM\Internal\Hydration\ObjectHydrator.php:75
C:\xampp\htdocs\lms-user-sml-feature\system\application\libraries\Doctrine\ORM\Internal\Hydration\AbstractHydrator.php:98
C:\xampp\htdocs\lms-user-sml-feature\system\application\libraries\Doctrine\ORM\AbstractQuery.php:530
C:\xampp\htdocs\lms-user-sml-feature\system\application\libraries\Doctrine\ORM\AbstractQuery.php:360

The following data is in the database:

<?xml version="1.0" encoding="UTF-8"?>
<dataset>
	<table name="user">
		<column>id</column>
		<column>mission_Statement</column>
		<column>first_name</column>
		<column>last_name</column>
		<column>initial</column>
		<column>email</column>
		<column>company</column>
		<column>picture</column>
		<column>bio</column>
		
		<row>
			<value>1</value>
			<value>Mission Statement 1</value>
			<value>First Name 1</value>
			<value>Last Name 1</value>
			<value>IN1</value>
			<value>email1@email.com</value>
			<value>Company 1</value>
			<value>Picture 1</value>
			<value>Bio 1</value>
		</row>
	</table>
	
	<table name="socialmedialink">
		<column>id</column>
		<column>title</column>
		<column>link</column>

		<row>
			<value>1</value>
			<value>Social Media Title 1</value>
			<value>Social Media Link 1</value>
		</row>
	</table>
	
	<table name="users_socialmedialinks">
		<column>user_id</column>
		<column>socialmedialink_id</column>

		<row>
			<value>1</value>
			<value>1</value>
		</row>
	</table>
</dataset>

[DDC-931] SchemaTool->dropSchema fails if the given schema doesn't exist

Wed, 22 Dec 2010 17:11:12 +0000

SchemaTool->dropSchema's documentation says:

 
Drops the database schema for the given classes.

In any way when an exception is thrown it is supressed since drop was issued for all classes of the schema and some probably just don't exist.

However, with a recent upgrade to 2.0-RC2, this doesn't work anymore. A PDO exception isn't caught if the specified table doesn't exist already.

 
exception 'PDOException' with message 'SQLSTATE[42S02]: Base table or view not found: 1051 Unknown table 'UserAddress'' in /usr/share/php/Doctrine/DBAL/Connection.php:577

I'm not sure if this was caused by the ORM update or if it's maybe somewhere inside DBAL, which I upgraded at the same time.

[DDC-944] MappingException::mappingNotFound() calls are wrong in ClassMetadataInfo

Tue, 21 Dec 2010 18:29:21 +0000

As you can see in:
https://github.com/doctrine/doctrine2/blob/master/lib/Doctrine/ORM/Mapping/ClassMetadataInfo.php
and:
https://github.com/doctrine/doctrine2/blob/master/lib/Doctrine/ORM/Mapping/MappingException.php
mappingNotFound() accepts now only 1 argument, but is called with 2; this leads to cryptic errors when the a field does not exist like:
Doctrine\ORM\Mapping\MappingException: No mapping found for field 'EntityClassName'