8000 Enforcing Abstract Entity in DiscriminatorMap is important for some operations · Issue #9142 · doctrine/orm · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
Enforcing Abstract Entity in DiscriminatorMap is important for some operations #9142
Closed
@olsavmic

Description

@olsavmic

Bug Report

Summary

Recent fix introduced in 2.10.2 9096: Fix SchemaValidator with abstract child class in discriminator map is a regression to the SchemaValidator as having all @Entity classes, including those that are non-instantiable (abstract) is important for some operation.

@beberlei already mentioned it here #8736 (comment)

I also mentioned this in the original issue (#8771 (comment)) regarding this change.

I'll try to prepare a convincing test case.

Q A
BC Break no
Version 2.10.2

Current behaviour

Abstract class marked with @Entity annotation does not have to be part of DiscriminatorMap (according to SchemaValidator)

Expected behavior

Only @MappedSuperclass does not have to be part of the SchemaValidator, missing @Entity is dangerous in some cases

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0