feat(query-engine-common): reduce duplicated code between `query-engine-node-api` and `query-engine-wasm` #4521

…ls on native

…asm32-unknown-unknown compilation

…github.com:prisma/prisma-engines into feat/sql-query-connector-on-wasm32-unknown-unknown

…o feat/query-core-on-wasm32-unknown-unknown

…ery-connector-on-wasm32-unknown-unknown

…o feat/query-core-on-wasm32-unknown-unknown

…github.com:prisma/prisma-engines into feat/sql-query-connector-on-wasm32-unknown-unknown

…o feat/query-core-on-wasm32-unknown-unknown

…quest-handlers-on-wasm32-unknown-unknown

…epare empty "wasm" module

…r" into "driver_adapters::error"

…pes"

…ltSet" to "driver_adapters::conversion::js_to_quaint"

…iver-adapters"

…nknown

…o feat/query-core-on-wasm32-unknown-unknown

…quest-handlers-on-wasm32-unknown-unknown

…nknown

…o feat/query-core-on-wasm32-unknown-unknown

…quest-handlers-on-wasm32-unknown-unknown

…eat/driver-adapters-on-wasm32-unknown-unknown

…o build"

… in a wasm32-compatible fashion

…at/query-engine-wasm32-unknown-unknown

1. Build schema and connect sequentually 2. Print full stacktrace for WASM error 3. Expand example to attempt a query

Replace `Instant::now` with a custom library, that will use appriate time/date functions for the platforms. For native, it is `std::time`, for WASM in should probably be `performance::now()` but it is a no-op stub for now.

…:prisma/prisma-engines into feat/query-engine-wasm32-unknown-unknown

…sultSet"

…at/query-engine-wasm32-unknown-unknown

Switch to sqlite so cloud services are not required Save schema to external file

Correctly gets to a point of starting the tranasction and executing the query, fails on parsing the results like normal queries do.

…dev development

…feature to example

…:prisma/prisma-engines into feat/query-engine-wasm32-unknown-unknown

…m32-unknown-unknown

…ntrolled spawns

…:prisma/prisma-engines into feat/query-engine-wasm32-unknown-unknown

ppy fixes

Strictly speaking, not related to wasm engine at all - we bumped `insta` at some point and that required adding `allow_duplicates` macro around the loop. Close prisma/team-orm#651

…:prisma/prisma-engines into feat/query-engine-wasm32-unknown-unknown

* I didn't have wasm-pack installed, let's fix that * Update wasm-bindgen-futures to 0.4.39 This includes rustwasm/wasm-bindgen#3203 that use queueMicrotask to transalate spawn_local rust code. This has fixed rustwasm/wasm-bindgen#2392 which was an issue about not being able to catch async wasm traps. This might (or not) have an effect on the issue we are trying to solve in here. * Revert "Update wasm-bindgen-futures to 0.4.39" This reverts commit 9a494dc. * Restart executor when it dies * Document Restartable * Remove async_panic_to_js_error in WASM query engine * Rename p -> process * Use tokio::sync::RwLock rather than futures::lock::Mutex * Better error messaging * Fixing clippy * Exclude unit tests for wasm32 when compiling the binary for other architectures

Removes following functionality from WASM engine: - GraphQL protocol - DMMF - SDL Schema Neither of the features are used by the client runtimes and thrid party clients don't and can not use WASM engine, so it is safe to remove.

…undefined"

…:prisma/prisma-engines into feat/query-engine-wasm32-unknown-unknown

This reverts commit 60b0d8c.

This reverts commit 481ba65.

…pendent "has_named_property" function

This reverts commit 28c6ff9.

…ic, when possible; apply clippy fixes

…, improve comments

…to unexpected case

…target-utils

…ne-wasm" and "query-engine-node-api"

…ry-engine-common

* qe-wasm: Partially fix the test suite 1. Bash script for build did not abort on error, hence sed error on linux went unnoticed. 2. We don't actually need sed trickery sincce `wasm-pack` has a flag for changing binary name. 3. `tracing` feature does not actually work on WASM even partially: it panics on `Instant` invokation as soon as first span is created. Since we are running tests with all preview features enabled, that means that practically any test panics now. Disabled it again. A lot of tests are still failing on ThreadRng invocation and stacktrace is not really helpful, but I still think it's better if we get it working. * Update query-engine/query-engine-wasm/build.sh

…ry-engine-common

…ct field by introducing *Native structs conditionally

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat(query-engine-common): reduce duplicated code between `query-engine-node-api` and `query-engine-wasm` #4521

feat(query-engine-common): reduce duplicated code between `query-engine-node-api` and `query-engine-wasm` #4521

Commits on Nov 10, 2023

Commits on Nov 13, 2023

Commits on Nov 14, 2023

Commits on Nov 15, 2023

Commits on Nov 16, 2023

Commits on Nov 17, 2023

Commits on Nov 20, 2023

Commits on Nov 21, 2023

Commits on Nov 22, 2023

Commits on Nov 23, 2023

Commits on Nov 24, 2023

Commits on Nov 27, 2023

Commits on Nov 28, 2023

Commits on Nov 29, 2023

Commits on Nov 30, 2023

Commits on Dec 4, 2023

Commits on Dec 5, 2023

Commits on Dec 6, 2023

Commits on Dec 11, 2023

Commits on Dec 15, 2023

feat(query-engine-common): reduce duplicated code between query-engine-node-api and query-engine-wasm #4521

feat(query-engine-common): reduce duplicated code between query-engine-node-api and query-engine-wasm #4521

Commits on Nov 10, 2023

Commits on Nov 13, 2023

Commits on Nov 14, 2023

Commits on Nov 15, 2023

Commits on Nov 16, 2023

Commits on Nov 17, 2023

Commits on Nov 20, 2023

Commits on Nov 21, 2023

Commits on Nov 22, 2023

Commits on Nov 23, 2023

Commits on Nov 24, 2023

Commits on Nov 27, 2023

Commits on Nov 28, 2023

Commits on Nov 29, 2023

Commits on Nov 30, 2023

Commits on Dec 4, 2023

Commits on Dec 5, 2023

Commits on Dec 6, 2023

Commits on Dec 11, 2023

Commits on Dec 15, 2023

feat(query-engine-common): reduce duplicated code between `query-engine-node-api` and `query-engine-wasm` #4521

feat(query-engine-common): reduce duplicated code between `query-engine-node-api` and `query-engine-wasm` #4521