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

[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

[AndriySvyryd]

Changing this would be a breaking change. One way to do it is to throw in validation if there's a clash.