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.

Sign up for GitHub

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

Jump to bottom

Migrations fail updating primary key constraint name when constraint is used in other tables #1940

Closed
tonykaralis opened this issue Oct 21, 2021 · 0 comments · Fixed by #1944
Closed

Migrations fail updating primary key constraint name when constraint is used in other tables #1940

tonykaralis opened this issue Oct 21, 2021 · 0 comments · Fixed by #1944
Labels
bug schema management
Milestone
4.0.2

Comments

@tonykaralis
Copy link
Contributor

Follow on from #1854.

Migrations are being generated when primary key constraint names have changed. When the constraint is not used in another table the migrations complete successfully, however when a constraint is used in another table the migrations fail.

The fix for this would end up in the Weasel project. See JasperFx/weasel#42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug schema management
Projects
None yet
Milestone
4.0.2
Development

Successfully merging a pull request may close this issue.

Used Weasel 1.0.4 with a fix for PK name migration with FKs JasperFx/marten
2 participants
@oskardudycz @tonykaralis