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

[multiSchema] check PSL validations for enum and composite type database name clashes #15626

Closed
tomhoule opened this issue Sep 30, 2022 · 1 comment · Fixed by prisma/prisma-engines#3269
Closed

[multiSchema] check PSL validations for enum and composite type database name clashes #15626

tomhoule opened this issue Sep 30, 2022 · 1 comment · Fixed by prisma/prisma-engines#3269
Assignees
@tomhoule
Labels
kind/improvement An improvement to existing feature and code. team/schema Issue for team Schema. topic: multiSchema multiple schemas topic: schema topic: validation
Milestone
4.5.0

Comments

@tomhoule
Copy link
Contributor

follow up to #15009
@tomhoule tomhoule added kind/improvement An improvement to existing feature and code. topic: schema topic: validation team/schema Issue for team Schema. topic: multiSchema multiple schemas labels Sep 30, 2022
@tomhoule
Copy link
Contributor Author

tomhoule commented Oct 5, 2022 •
edited

Additionally: from slack (@Jolg42 https://prisma-company.slack.com/archives/C02FNFLDUS3/p1664544204148229)

So we have a mutli-schema with 2 models
User -> schema base
Post -> schema transactionalWe do @@Map("some_table") on both of them.In theory it should work because it’s 2 different > database schemas? but it errors

@Jolg42 Jolg42 added this to the 4.5.0 milestone Oct 5, 2022
@tomhoule tomhoule self-assigned this Oct 5, 2022
@tomhoule tomhoule mentioned this issue Oct 6, 2022
Merged
tomhoule added a commit to prisma/prisma-engines that referenced this issue Oct 6, 2022
@tomhoule
psl: take @@Schema into account in constraint & enum name clashes
9491fc1 
closes prisma/prisma#15626
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tomhoule tomhoule

Labels
kind/improvement An improvement to existing feature and code. team/schema Issue for team Schema. topic: multiSchema multiple schemas topic: schema topic: validation
Projects
None yet
Milestone
4.5.0
Development

Successfully merging a pull request may close this issue.

psl: take @@Schema into account in constraint & enum name clashes prisma/prisma-engines
2 participants
@Jolg42 @tomhoule