Doctrine 2 - ORM

addFilterConstraint is called with wrong ClassMetadata, if Entity uses inheritance

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Invalid
  • Affects Version/s: 2.3.2
  • Fix Version/s: None
  • Component/s: ORM
  • Security Level: All
  • Labels:

Description

When using the filter system to modify the generated SQL the addFilterConstraint method always receives the metadata of the parent object. Both for Joined and Single Table Inheritance, which is not helpful if you want to do something based on the entity, but for example the parent entity does not fulfill the prequisites.

Activity

People

  • Assignee:
    Benjamin Eberlei
    Reporter:
    Philipp Dobrigkeit
Vote (0)
Watch (6)

Dates

  • Created:
    Updated:
    Resolved: