edgedb-go
edgedb-go copied to clipboard
The official Go client library for EdgeDB
This change implements the default behavior outlined in https://github.com/edgedb/edgedb/discussions/4244. All arguments and options to the generator command are left for future work along with query hashing. The [documentation](https://github.com/edgedb/edgedb-go/pull/236/files#diff-43b8e20634ba03cc187345a9c8ac57669ba567a358d5cfe83e2ed86325362bc8), [help text](https://github.com/edgedb/edgedb-go/pull/236/files#diff-7df6c5ada0b868390ac839ba9e93f37fd6c19a264cdcf317a33561167cea9494R54),...
[The docs](https://www.edgedb.com/docs/clients/go/api#type-retryoptions) mention a default constructor for RetryOptions Looks like #205 was never merged
Something better than string concatenation for dynamic query construction.
The example error below should only suggest `edgedb.OptionalDuration` because the field is not required. ``` 2022/06/29 13:02:06 edgedb.BinaryProtocolError: building decoder from ParameterStatus state_description: expected state.config.durprop to be edgedb.Duration or edgedb.OptionalDuration...
see also https://github.com/edgedb/edgedb-go/issues/228#issuecomment-1167199853_
I have yet to find a way to pass a slice of edgedb.UUIDs to *edgedb.Client.Query.
Added a link to docs as readme doesn't include everything. Also updated example code as copy pasting one currently there gave errors that `edgedb` is not in scope. Site docs...
While benchmarking the client I noticed that every connection release triggered parsing of the `system_config` server setting to get the idle connection timeout. This in turn requires building a brand...
This caused a bit of confusion when tests started failing when moving unit tests into a linux container from my mac workstation. Not the fault of edgedb-go but may be...