Elixir client for EdgeDB
2.0
.EdgeDB.MultiRange
type to represent multiranges from EdgeDB 4.0
.EdgeDB.Object.id/1
to fetch ID from an EdgeDB.Object
if it was returned from the query.EdgeDB.ConfigMemory.new/1
to create a new instance of t:EdgeDB.ConfigMemory.t/0
.Elixir v1.16
.t:EdgeDB.Object.t/0
to be opaque
.:id
field into objects so that this no longer happens.EdgeDB.with_config/2
/EdgeDB.without_config/2
,
EdgeDB.with_globals/2
/EdgeDB.without_globals/2
and
EdgeDB.with_module_aliases/2
/EdgeDB.without_module_aliases/2
.cal::date_duration
EdgeDB type via EdgeDB.DateDuration
structure.EdgeDB 3.0
.ext::pgvector::vector
type.Enumerable
protocol for EdgeDB.Set
.EdgeDB.State
to EdgeDB.Client.State
, EdgeDB.with_state/2
to
EdgeDB.with_client_state/2
, :state
option to :client_state
.MIT
to Apache 2.0
.db_connection
to 2.5
.EdgeDB.Object
that equals to an empty set.EdgeDB.Error
exception during parameters encoding,
which caused throwing an exception for non-!
functions.EdgeDB
API with wrong module names.EdgeDB.subtransaction/2
, EdgeDB.subtransaction!/2
functions and other mentions of
subtransactions support in the client.:raw
option from EdgeDB.query*
functions as well as access to EdgeDB.Query
and EdgeDB.Result
.EdgeDB.Error
.EdgeDB.Client
module that is acceptable by all EdgeDB
API.:max_concurrency
option to start pool to control max connections count in EdgeDB.Pool
.DBConnection.Pool
to EdgeDB.Pool
.EdgeDB.Pool
to be "real" lazy and dynamic: all idle connections that EdgeDB wants to drop
will be disconnected from the pool, new connections will be created only on user queries
depending on EdgeDB concurrency suggest as soft limit and :max_concurrency
option as hard limit
of connections count.EdgeDB.transaction/3
, EdgeDB.subtransaction/2
and EdgeDB.subtransaction!/2
from t:DBConnection.t/0
to t:EdgeDB.Client.t/0
.EdgeDB.connection/0
to t:EdgeDB.client/0
.EdgeDB.edgedb_transaction_option/0
to t:EdgeDB.Client.transaction_option/0
.EdgeDB.retry_option/0
to t:EdgeDB.Client.retry_option/0
.EdgeDB.retry_rule/0
to t:EdgeDB.Client.retry_rule/0
.EdgeDB.WrappedConnection
module in favor of EdgeDB.Client
.EdgeDB 2.0
with new binary protocol.EdgeDB.State
.EdgeDB.Range
type to represent ranges from EdgeDB 2.0
.EdgeDB.execute/4
and EdgeDB.execute!/4
.io_format
option to output_format
.EdgeDB.Object.to_map/1
and EdgeDB.NamedTuple.to_map/1
functions.std::datetime
EdgeDB type via Timex.Duration
structure.new/2
function, that will return the EdgeDB.Error
exception.EdgeDB.Error
functions that create new exceptions.EdgeQL
queries to be lowercase.EdgeDB.Error.inheritor?/2
to work with generated module names for EdgeDB exceptions instead of atoms.:repeatable_read
option for transaction isolation mode from EdgeDB.edgedb_transaction_option/0
.std::str
from std::uuid
to str::str
.EdgeDB.Protocol.Codec.decode/3
implementation and used the wrong protocol.EdgeDB.Object.fields/2
, EdgeDB.Object.properties/2
, EdgeDB.Object.links/1
and EdgeDB.Object.link_properties/1
functions to inspect the fields of the object.EdgeDB.Error.inheritor?/2
function to check if the exception is an inheritor of another EdgeDB error.EdgeDB.Sandbox
module for use in tests involving database modifications.EdgeDB.Pool
to support dynamic resizing of the connection pool via messages from EdgeDB server.EdgeDB.Object
properties equal to an empty EdgeDB.Set
.REPEATABLE READ
mode, because only SERIALIZABLE
is supported by EdgeDB 1.0
(REPEATABLE READ
was dropped in EdgeDB 1.3
).EdgeDB.NamedTuple
(EdgeDB.NamedTuple.to_tuple/1
, EdgeDB.NamedTuple.keys/1
), including Enumerable
protocol implementation.Access
behaviour for EdgeDB.Object
to improve fields access performance.