Doctrine Project

[DDC-1019] Double quotation mark mysql query error on orm:convert-mapping --from-database

Duplicate — Mon, 7 Feb 2011 05:39:36 +0000

By executing this command php doctrine orm:convert-mapping --from-database yml yaml/ I get this error:

 
PHP Fatal error:  Uncaught exception 'PDOException' with message 'SQLSTATE[42S22]: Column not found: 1054 Unknown column 'BASE TABLE' in 'where clause'' in doctrine2-orm/lib/vendor/doctrine-dbal/lib/Doctrine/DBAL/Connection.php:577
Stack trace:
#0 doctrine2-orm/lib/vendor/doctrine-dbal/lib/Doctrine/DBAL/Connection.php(577): PDO->query('SHOW FULL TABLE...')
#1 doctrine2-orm/lib/vendor/doctrine-dbal/lib/Doctrine/DBAL/Connection.php(532): Doctrine\DBAL\Connection->executeQuery('SHOW FULL TABLE...', Array)
#2 doctrine2-orm/lib/vendor/doctrine-dbal/lib/Doctrine/DBAL/Schema/AbstractSchemaManager.php(194): Doctrine\DBAL\Connection->fetchAll('SHOW FULL TABLE...')
#3 doctrine2-orm/lib/Doctrine/ORM/Mapping/Driver/DatabaseDriver.php(76): Doctrine\DBAL\Schema\AbstractSchemaManager->listTableNames()
#4 doctrine2-orm/lib/vendor/doctrine-dbal/lib/Doctrine/DBAL/Connection.php on line 577

After var_dump the $query variable doctrine2-orm/lib/vendor/doctrine-dbal/lib/Doctrine/DBAL/Connection.php on line 577 string(48) "SHOW FULL TABLES WHERE Table_type = "BASE TABLE"" you can see that BASE TABLE is in double quotations marks.
I replaced them with single quotation marks SHOW FULL TABLES WHERE Table_type = 'BASE TABLE' and executed the statement on the mysql server, no error!

Please replace the double quotation marks in the query with single quotation marks.

[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-990] Update QueryBuilder reference doc

Sun, 23 Jan 2011 05:16:42 +0000

i had a hard time finding how to limit the number of results for querybuilder.

the reference does not say how to do it
http://www.doctrine-project.org/docs/orm/2.0/en/reference/query-builder.html

google brought up that its called setMaxResult, which works fine:
http://www.doctrine-project.org/api/orm/2.0/doctrine/orm/querybuilder.html

maybe the reference is missing more things from the code...

(btw: calling it just limit would have been very intuitive for sql people

[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-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-975] Notice in SchemaTool when using assigned id string without length and auto-join column generation

Thu, 13 Jan 2011 15:46:09 +0000

Notice in SchemaTool when using assigned id string without length and auto-join column generation

[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-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-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-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-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-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-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-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-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-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'

[DDC-932] Schema problem with Postgresql

Tue, 28 Dec 2010 23:18:23 +0000

Hi, I have a problem when using doctrine 2 with schema in Postgresql.

This is my php mapping:

<?php

use Doctrine\ORM\Mapping\ClassMetadataInfo;

$metadata->setInheritanceType(ClassMetadataInfo::INHERITANCE_TYPE_NONE);
$metadata->setPrimaryTable(array(
    'name' => 'sales.mdp',
));

$metadata->setChangeTrackingPolicy(ClassMetadataInfo::CHANGETRACKING_DEFERRED_IMPLICIT);
$metadata->setIdGeneratorType(ClassMetadataInfo::GENERATOR_TYPE_SEQUENCE);
$metadata->setSequenceGeneratorDefinition(array(
        'sequenceName'   => 'sales.mdp_id_seq',
        'allocationSize' => 10,
        'initialValue'   => 1,
    ));
    
$metadata->mapField(array(
   'id'         => true,
   'fieldName'  => 'id',
   'columnName' => 'id',
   'type'       => 'integer',
  ));

I can generate tables successfully with orm:schema-tool:create.
I don't edit anything, and just try to orm:schema-tool:update, the output should be:

Nothing to update. The database is in sync with the current entity metadata.

But I get:

Updating database schema...

  [PDOException]

  SQLSTATE[42P07]: Duplicate table: 7 ERROR:  relation "mdp_id_seq" already exists

my orm:schema-tool:update --dump-sql outputs

CREATE SEQUENCE sales.mdp_id_seq INCREMENT BY 10 MINVALUE 1 START 1;
CREATE TABLE sales.mdp (id INT NOT NULL, rrn VARCHAR(50) NOT NULL, model VARCHAR(255) DEFAULT NULL, tipe VARCHAR(255) DEFAULT NULL, warna VARCHAR(50) DEFAULT NULL, nama_pelanggan VARCHAR(255) DEFAULT NULL, sales VARCHAR(255) DEFAULT NULL, keterangan TEXT DEFAULT NULL, tanggal DATE NOT NULL, created_at TIMESTAMP(0) WITHOUT TIME ZONE DEFAULT NULL, PRIMARY KEY(id));
CREATE UNIQUE INDEX sales_mdp_rrn_uniq ON sales.mdp (rrn)

I upload my files in attachment. Please advice, thanks.

[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-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-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-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-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-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-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-166] When entity is moved from one collection to another, it is still considered "orphaned"

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

If I remove an entity from a PersistentCollection, the UnitOfWork marks is as "orphaned" (assuming I set that in my entity). If I then move the entity to another collection, this status doesn't get removed, and the UnitOfWork deletes it.