edgedb-rust
edgedb-rust copied to clipboard
edgedb
The official Rust binding for EdgeDB
**Describe the bug** Trying to use `edgedb_protocol::model::Duration`, I get the following error: ``` error: Some( WrongType { unexpected: "BaseScalar(BaseScalarTypeDescriptor { id: BaseScalar(duration) })", expected: "cal::date_duration", }, ), headers: {}, fields:...
As far I can tell there's no way to use link properties in the derive macro currently, instead you need to map from `edged_protocol::Value` into the type you want in...
Currently `QueryArg`'s definition is pretty opaque and how an implementor is supposed to implement `encode_slot` and `check_descriptor` is undocumented, and a user is mostly expected to use this trait through...
We has always wanted to expose bindings under `edgedb` crate instead of the `edgedb-tokio/whatever`. But the structure of that is not very clear. Here is a sketch of my current...
The idea is that when one does a query via Rust (or perhaps any other type-safe language), they describe shape twice: ```rust struct User { first_name: String, last_name: String, articles:...
# The Problem In Rust `Vec` is the same type that can be used both for `Array` and `pgvector`. But our current code assumes single Rust type == single EdgeDB...
Would it be possible to support something similar to sqlx? I think it could be really nice to have this feature when it comes to have a great developer experience...
Currently in docs we see: ``` impl Queryable for T ``` Which doesn't give a list of scalar types that implement that trait. Note: I don't think that alternative of...
It seems, the [Queryable](https://docs.rs/edgedb-protocol/0.4.0/edgedb_protocol/queryable/trait.Queryable.html) trait isn't implemented for [edgedb_protocol::value::Value](https://docs.rs/edgedb-protocol/0.4.0/edgedb_protocol/value/enum.Value.html). `Value` would be quite valuable for debugging, logging, and so on.
This would offer greater flexibilty for serializing any array-like construct. For example, it would remove the need for intermediate allocations when transforming data before serializing it.
