Xtdb
Types
A connection to one database, dbName.
A statement on a Connection.
Properties
The names of the databases this node currently serves.
The port the healthz server bound to, or -1 if healthz isn't configured on this node.
Functions
user, taken at its word: neither credentials nor the node's authn rules are checked, so this authenticates any user, superuser included. Where the rules should decide, consult authMethodFor first.
The client clientId, having verified clientSecret with the node's authenticator (the OAuth client-credentials flow). The principal's user id is the one the authenticator resolves for that client.
The authentication method the node's configured authn rules ask of a caller claiming user from remoteAddress, or null if no rule matches and the caller is to be rejected.
Opens an in-process connection to the named database.
Opens an in-process connection to the named database as principal: the connection's Connection.user is the principal's user id. The node doesn't check principal — obtain one from the authenticate… methods below.
The transaction goes to TxOpts.dbName, defaulting to the primary database xtdb, and may only refer to tables within it — see Connection.
Each database's latest-completed transaction, per partition.
Starts the OAuth device-authorisation flow for user. Show the caller DeviceAuth.url, then call DeviceAuth.await, which blocks until they approve.
The transaction goes to TxOpts.dbName, defaulting to the primary database xtdb, and may only refer to tables within it — see Connection.