Doctrine 2 - ORM

InvalidArgumentException: New entity detected during merge. Persist the new entity before merging.

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 2.0-BETA1
  • Component/s: None
  • Security Level: All
  • Labels:
    None
  • Environment:
    win XP SP3, PHP 5.3.1, MySQL

Description

I have attached my test project, except 'Doctrine' folder with Doctrine 2 project.
What I did:
1. I created schema manually (user create.sql file)
2. I generated model classes (by doctrine-cli.php script)
3. Made a little changes in annotations (I just added OneToMany between user and phone)
4. Run script test.php
Steps for reproducing:
1. create schema from create.sql file
2. fix connection string in dbconfig.php
3. run test.sql

Simple workaroung for me is to make all private fields as protected.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Valery Dubrava added a comment - - edited

When I changed access for the user's field from private to protected, I faced with another error:
Fatal error: Call to a member function load() on a non-object in ...\models\proxies\UserProxy.php on line 17

Call Stack:
0.0003 338752 1.

{main}

() \test.php:0
0.0928 3940528 2. Proxies\UserProxy->getPhones() \test.php:29
0.0928 3940528 3. Proxies\UserProxy->_load() \models\proxies\UserProxy.php:40

Show
Valery Dubrava added a comment - - edited When I changed access for the user's field from private to protected, I faced with another error: Fatal error: Call to a member function load() on a non-object in ...\models\proxies\UserProxy.php on line 17 Call Stack: 0.0003 338752 1. {main} () \test.php:0 0.0928 3940528 2. Proxies\UserProxy->getPhones() \test.php:29 0.0928 3940528 3. Proxies\UserProxy->_load() \models\proxies\UserProxy.php:40
Hide
Permalink
Benjamin Eberlei added a comment -

Thank you for reporting this issue.

Please create a unit-test, in the schema of tests\Doctrine\Tests\ORM\Functional\Ticket and attach it as a .patch or .diff or .php file. This is not a minimal re-produce case that can be easily understood or run by us.

Show
Benjamin Eberlei added a comment - Thank you for reporting this issue. Please create a unit-test, in the schema of tests\Doctrine\Tests\ORM\Functional\Ticket and attach it as a .patch or .diff or .php file. This is not a minimal re-produce case that can be easily understood or run by us.
Hide
Permalink
Benjamin Eberlei added a comment -

Are you by any chance still using ALPHA3 ?

Show
Benjamin Eberlei added a comment - Are you by any chance still using ALPHA3 ?
Hide
Permalink
Benjamin Eberlei added a comment -

This issue is two-fold:

  • You are not allowed to use private variables when you want to serialize/unserialize the entity (because of proxy instances)
  • There was an error when unserializing a proxy class with protected variables, a call to the "proxied" methods fatals because the entity persister does not exist anymore.

The fatal error issue is fixed, the first point is clearly documented now. Issue closed.

Show
Benjamin Eberlei added a comment - This issue is two-fold: You are not allowed to use private variables when you want to serialize/unserialize the entity (because of proxy instances) There was an error when unserializing a proxy class with protected variables, a call to the "proxied" methods fatals because the entity persister does not exist anymore. The fatal error issue is fixed, the first point is clearly documented now. Issue closed.
Hide
Permalink
Valery Dubrava added a comment - - edited

Thanks again!
But, may be it would be better to correct code generation for generating classes with protected fields?
@Benjamin Eberlei:
I use trunk, I don't know what version is in trunc =)

Show
Valery Dubrava added a comment - - edited Thanks again! But, may be it would be better to correct code generation for generating classes with protected fields? @Benjamin Eberlei: I use trunk, I don't know what version is in trunc =)
Hide
Permalink
Benjamin Eberlei added a comment -

@Valery: The database to annotation converter is not a tool that you should use during your development. It is to generate the entities once from a legacy database schema. Doctrine 2s preferred way is to generate the schema FROM the entities using SchemaTool, not the other way round.

Show
Benjamin Eberlei added a comment - @Valery: The database to annotation converter is not a tool that you should use during your development. It is to generate the entities once from a legacy database schema. Doctrine 2s preferred way is to generate the schema FROM the entities using SchemaTool, not the other way round.
Hide
Permalink
Valery Dubrava added a comment -

Right! I agree, but in any case, this tool exists, and many people will use it. Now, this tool generates classes without supporting of serialization. It looks like a bug..

Show
Valery Dubrava added a comment - Right! I agree, but in any case, this tool exists, and many people will use it. Now, this tool generates classes without supporting of serialization. It looks like a bug..

People

  • Assignee:
    Benjamin Eberlei
    Reporter:
    Valery Dubrava
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: