Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
maumar opened this issue Mar 2, 2025 · 0 comments

Comments

@maumar
Copy link
Contributor

maumar commented Mar 2, 2025

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant