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

Allow setting the length prefix on Unsupported fields on MySQL #13786

Closed
pimeys opened this issue Jun 13, 2022 · 0 comments · Fixed by prisma/prisma-engines#2976
Closed

Allow setting the length prefix on Unsupported fields on MySQL #13786

pimeys opened this issue Jun 13, 2022 · 0 comments · Fixed by prisma/prisma-engines#2976
Labels
kind/improvement An improvement to existing feature and code. team/schema Issue for team Schema. topic: breaking change topic: extendedIndexes topic: prisma4 topic: Unsupported Scalar pseudo type `Unsupported` topic: validation
Milestone
4.0.0

Comments

@pimeys
Copy link
Contributor

pimeys commented Jun 13, 2022 •
edited by janpio

Certain types, such as geometry, allows setting the length argument in an index using that column.
Prisma currently gives a validation error for these, but maybe we should allow setting the length for the unsupported fields.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/improvement An improvement to existing feature and code. team/schema Issue for team Schema. topic: breaking change topic: extendedIndexes topic: prisma4 topic: Unsupported Scalar pseudo type `Unsupported` topic: validation
Projects
None yet
Milestone
4.0.0
Development

Successfully merging a pull request may close this issue.

Allow length prefix on unsupported types indexing prisma/prisma-engines
2 participants
@pimeys @janpio