entity persister gets superclasses' metadata for proxied subclass entity

Details

Type: Bug
Status: Resolved
Priority: Critical
Resolution: Fixed
Affects Version/s: 2.0.3, 2.0.4, 2.0.5
Fix Version/s: 2.0.6, 2.1
Component/s: ORM
Security Level: All
Labels:
None
Environment:
PHP 5.3.6 on Debian Lenny & WinXP, PostgreSQL 8.4 & SQLite 3

Description

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.

Options
- Sort By Name
- Sort By Date
- Ascending
- Descending
- Download All

Attachments

testcase.zip

20/May/11 10:15 PM

5 kB

Stan Imbt

Activity

Ascending order - Click to sort in descending order

Stan Imbt made changes - 20/May/11 10:17 PM

Field	Original Value	New Value
Description	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.	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.