You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The constraints argument is missing in most if not all instances of generated migrationBuilder.CreateTable calls. Especially table.PrimaryKey types.
I believe #68 may be related to this. That deals with conventional detection of PK, but it seems to be all PK constraints are actually missing in the 5.0.3-alpha2 release, even those that are manually demarked with the [<Key>] annotation.
To Reproduce
Steps to reproduce the behavior:
Create new table which includes a Primary Key annotated with [<Key>] in type definition
Create new migration
Observe the lack of a constraints argument in CreateTable call
Perform database migration
If successful, observe that no Primary Key is defined for database, and if Key was int type observe failure due to the inclusion of AUTO INCREMENT that is illegal in many databases engines outside of PK.
Expected behavior
Inclusion of a clause similar to that seen in older 3.1.12 release
Describe the bug
The
constraints
argument is missing in most if not all instances of generatedmigrationBuilder.CreateTable
calls. Especiallytable.PrimaryKey
types.I believe #68 may be related to this. That deals with conventional detection of PK, but it seems to be all PK constraints are actually missing in the
5.0.3-alpha2
release, even those that are manually demarked with the[<Key>]
annotation.To Reproduce
Steps to reproduce the behavior:
[<Key>]
in type definitionconstraints
argument inCreateTable
callKey
wasint
type observe failure due to the inclusion ofAUTO INCREMENT
that is illegal in many databases engines outside of PK.Expected behavior
Inclusion of a clause similar to that seen in older
3.1.12
releaseThe text was updated successfully, but these errors were encountered: