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

Check validity of having Unique Constraint and Primary Key Constraint on the same Column on SqlServer #8463

Closed
do4gr opened this issue Jul 27, 2021 · 0 comments · Fixed by prisma/prisma-engines#2117
Assignees
Labels
bug/2-confirmed Bug has been reproduced and confirmed. kind/bug A reported bug. team/schema Issue for team Schema. topic: sql server Microsoft SQL Server
Milestone

Comments

@do4gr
Copy link
Member

do4gr commented Jul 27, 2021

Bug description

We currently have a datamodel validation that rejects that. Introspection CI does introspect it though on one of our sample schemas. Either the validation is wrong and needs to be removed or introspection is wrong and should not output such a datamodel.
Screen Shot 2021-07-27 at 13 21 34

How to reproduce

Expected behavior

No response

Prisma information

Environment & setup

  • OS:
  • Database:
  • Node.js version:

Prisma Version


@do4gr do4gr added the kind/bug A reported bug. label Jul 27, 2021
@Jolg42 Jolg42 added the team/schema Issue for team Schema. label Jul 27, 2021
@thebiglabasky thebiglabasky added topic: sql server Microsoft SQL Server bug/2-confirmed Bug has been reproduced and confirmed. labels Jul 28, 2021
@thebiglabasky thebiglabasky added this to the 2.29.0 milestone Jul 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug/2-confirmed Bug has been reproduced and confirmed. kind/bug A reported bug. team/schema Issue for team Schema. topic: sql server Microsoft SQL Server
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants