Skip to content

By convention we generate ambiguous table name for some models with owned collections #35710

@maumar

Description

@maumar

When generating table name for owned collection (which needs a separate table) we generate the name based on collections only, which may lead to name clashes.

e.g.

entity -> OwnedReference1 -> OwnedCollection
and
entity -> OwnedReference2 -> OwnedCollection

will try to use same table name (entity_OwnedCollection)

workaround is to set the table name explicitly

Metadata

Metadata

Assignees

Type

No fields configured for Task.

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions