Support PrimaryKeyConstraintName for EntitySchema #9309
Description
Feature Description
The Problem
At #8900 the primaryKeyConstraintName support was added to decorator-based models, but there is no way to provide primaryKeyConstraintName using EntityDefinition approach.
The Solution
Make sense to add primaryKeyConstraintName key to the EntityDefinition schema. This way we will be able to pass an exact constraint name to the schema so the migration:generate script will use it
Considered Alternatives
Currently, the only alternative here is to get rid of EntitySchema and use classes & decorators only for this minor thing.
Additional Context
Let me know if something is needed
Relevant Database Driver(s)
| DB Type | Relevant |
|---|---|
aurora-mysql |
no |
aurora-postgres |
no |
better-sqlite3 |
no |
cockroachdb |
no |
cordova |
no |
expo |
no |
mongodb |
no |
mysql |
no |
nativescript |
no |
oracle |
no |
postgres |
yes |
react-native |
no |
sap |
no |
spanner |
no |
sqlite |
no |
sqlite-abstract |
no |
sqljs |
no |
sqlserver |
no |
Are you willing to resolve this issue by submitting a Pull Request?
- ✖️ Yes, I have the time, and I know how to start.
- ✖️ Yes, I have the time, but I don't know how to start. I would need guidance.
- ✖️ No, I don’t have the time, but I can support (using donations) development.
- ✅ No, I don’t have the time and I’m okay to wait for the community / maintainers to resolve this issue.