-
Notifications
You must be signed in to change notification settings - Fork 235
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
feat(prisma-schema-wasm): add get_datamodel method #4946
Conversation
CodSpeed Performance ReportMerging #4946 will not alter performanceComparing Summary
|
91a8585
to
5aa1a0e
Compare
WASM Query Engine file Size
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it expected to (temporarily) fail on ecosystem-tests?
@jkomyno looks unrelated |
Add `get_datamodel` method to get just that part of the DMMF without building, serializing, sending across WASM boundary and then deserializing the whole DMMF.
5aa1a0e
to
e7f1052
Compare
@jkomyno everything passes on another try (except one job failing due to file name being too long on windows): https://github.com/prisma/ecosystem-tests/actions/runs/9864026111/job/27238821658 |
Add
get_datamodel
method to get just that part of the DMMF without building, serializing, sending across WASM boundary and then deserializing the whole DMMF.We will also need information about the indexes (currently only unique indexes are included there) and, later, spans of the entities in the schema file.