-
Notifications
You must be signed in to change notification settings - Fork 244
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
fix(quaint/DA): handle JSON parsing engines side so that we can correctly handle i64
s
#4883
Conversation
unexclude common_types test for pg, neon, and PS
CodSpeed Performance ReportMerging #4883 will not alter performanceComparing Summary
|
WASM Query Engine file Size
|
i64
si64
s
I think we can also get rid of this block in |
✅ WASM query-engine performance won't change substantially (0.987x)Full benchmark report
After changes in 374fc28 |
remove special handling for "$__prisma_null"
… <-> DA contract. To be re-enabled and re-evaluated in a follow-up PR per convo with @SevInf
Co-authored-by: Serhii Tatarintsev <tatarintsev@prisma.io>
@@ -59,6 +59,7 @@ jobs: | |||
|
|||
- name: Run benchmarks | |||
id: bench | |||
if: false |
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.
Note for posteriority: temprarily disabled, as we can't run benchmarks against older version of WASM engine without using driver adapters too: https://github.com/prisma/team-orm/issues/1152
…an correctly handle `i64`s (#4883)" This reverts commit f742678. Temporary reverting the change. It is interdependent with prisma/prisma#24269 and neither PR works correctly without the other. The plan was to let engines CI to temporarily go red and fix it immediately by merging client PR. However, engine release pipeline is broken for unrelated reason and this is not possible. Just to limit amount of broken things in progress, we are reverting original PR. It is expected we restore it with no changes once release pipeline is fixed.
…an correctly handle `i64`s (#4883)" (#4886) This reverts commit f742678. Temporary reverting the change. It is interdependent with prisma/prisma#24269 and neither PR works correctly without the other. The plan was to let engines CI to temporarily go red and fix it immediately by merging client PR. However, engine release pipeline is broken for unrelated reason and this is not possible. Just to limit amount of broken things in progress, we are reverting original PR. It is expected we restore it with no changes once release pipeline is fixed.
…ctly handle `i64`s (#4883) * One half of the fix for: prisma/prisma#23926 * Unexcludes pg, neon, and PS for the through_relations::common_types test * Instead of receiving pre-handled JSON by DAs, we now expect strings and will perform JSON parsing in Quaint. * Removed special handling for "$__prisma_null" due to the aforementioned * Temporarily disable wasm-benchmarks due to breaking change in engines <-> DA contract. To be re-enabled and re-evaluated in a follow-up PR per convo with @SevInf --------- Co-authored-by: Serhii Tatarintsev <tatarintsev@prisma.io>
* One half of the fix for: prisma/prisma#23926 * Unexcludes pg, neon, and PS for the through_relations::common_types test * Instead of receiving pre-handled JSON by DAs, we now expect strings and will perform JSON parsing in Quaint. * Removed special handling for "$__prisma_null" due to the aforementioned * Temporarily disable wasm-benchmarks due to breaking change in engines <-> DA contract. To be re-enabled and re-evaluated in a follow-up PR per convo with @SevInf --------- Co-authored-by: Sophie <29753584+Druue@users.noreply.github.com>
unexclude
common_types
test for pg, neon, and PSrelated prisma/prisma#23926