David Bottiau

Unfortunately, `x86_64-unknown-linux-gnu` is not a valid/current target when using the `rust-build/rust-build.action` GitHub action. I will try to switch to an alternate GitHub action that support more targets.

Hi @senpro-ingwersenk This is an excellent idea. I published the current release and the preview releases (for alpha & beta versions of surrealdb) of `surrealdb-migrations` as Docker images on Docker...

Hello, `Query` is made to interpolate queries while `RawQuery` exist for scenario where you just pass the plain string query. The first one will interpret variables and replace them with...

Hello @J05HM0N5TER Well, this is an interesting idea. However, the core database does not support this behavior at the moment. If you want to see something like this, I suggest...

The `Upsert` or any other method is using the SurealDB `rpc` endpoint. You can find the docs here https://surrealdb.com/docs/surrealdb/integration/rpc These methods only return the `AFTER` value. If you want to...

I am not sure to see where the issue lies here. Some reviews about the code example you provided: * The `surrealDbClient` client is created from options, it will automatically...

`array::map` can indeed be useful in many occasions. The main challenge of this feature is the way to write closure. Since `$value` is already used in some statements, my current...

Well done @kearfy

Happened to have the same issue when migrated to Rust edition 2024.

I agree that if the `customFetch` handles error, we should be able to export a `Promise` of the type of the `200` data type, otherwise it should naturally default to...