(add-predicate-to-idx db pred-id)
(blank-db conn network dbid schema-cache current-db-fn)
(forward-time-travel db tt-id flakes)
Returns a core async chan with a new db based on the provided db, including the provided flakes. Flakes can contain one or more 't's, but should be sequential and start after the current 't' of the provided db. (i.e. if db-t is -14, flakes 't' should be -15, -16, etc.). Remember 't' is negative and thus should be in descending order.
A tt-id (time-travel-id), if provided, can be any unique identifier of any type and is required. It must be unique (to the computer/process) to avoid any query caching issues.
A forward-time-travel dbf can be further forward-time-traveled. If a tt-id is provided, ensure it is unique for each successive call.
A forward-time travel DB is held in memory, and is not shared across servers. Ensure you have adequate memory to hold the flakes you generate and add. If access is provided via an external API, do any desired size restrictions or controls within your API endpoint.
Remember schema operations done via forward-time-travel should be done in a 't' prior to the flakes that end up requiring the schema change.
Returns a core async chan with a new db based on the provided db, including the provided flakes. Flakes can contain one or more 't's, but should be sequential and start after the current 't' of the provided db. (i.e. if db-t is -14, flakes 't' should be -15, -16, etc.). Remember 't' is negative and thus should be in descending order. A tt-id (time-travel-id), if provided, can be any unique identifier of any type and is required. It must be unique (to the computer/process) to avoid any query caching issues. A forward-time-travel dbf can be further forward-time-traveled. If a tt-id is provided, ensure it is unique for each successive call. A forward-time travel DB is held in memory, and is not shared across servers. Ensure you have adequate memory to hold the flakes you generate and add. If access is provided via an external API, do any desired size restrictions or controls within your API endpoint. Remember schema operations done via forward-time-travel should be done in a 't' prior to the flakes that end up requiring the schema change.
(forward-time-travel-db? db)
Returns true if db is a forward time travel db.
Returns true if db is a forward time travel db.
(graphdb? db)
(new-empty-index conn index-configs network dbid idx)
(new-novelty-map index-configs)
(subid db ident strict?)
Returns subject ID of ident as async promise channel. Closes channel (nil) if doesn't exist, or if strict? is true, will return exception.
Returns subject ID of ident as async promise channel. Closes channel (nil) if doesn't exist, or if strict? is true, will return exception.
(validate-ledger-ident ledger)
Returns two-tuple of [network name-or-dbid] if db-ident is valid.
Will ignore a direct db name reference (prefixed with '_') Otherwise throws.
Returns two-tuple of [network name-or-dbid] if db-ident is valid. Will ignore a direct db name reference (prefixed with '_') Otherwise throws.
(validate-ledger-name ledger-id type)
Returns when ledger name is valid. Otherwise throws.
Returns when ledger name is valid. Otherwise throws.
(with db block flakes)
Returns db 'with' flakes added as a core async promise channel. Note this always does a re-sort.
Returns db 'with' flakes added as a core async promise channel. Note this always does a re-sort.
(with-t db flakes)
Processes a single transaction, adding it to the DB. Assumes flakes are already properly sorted.
Processes a single transaction, adding it to the DB. Assumes flakes are already properly sorted.
cljdoc is a website building & hosting documentation for Clojure/Script libraries
× close