datahike.pg.catalog.objects — org.replikativ/pg-datahike 0.1.194

Persistent PostgreSQL catalog identities for user-defined objects.

PostgreSQL identifies an object by (catalog relation OID, object OID), with an optional sub-object number for columns. Keeping that shape here lets routines, triggers, dependencies, and future catalog work share one transactional identity model instead of inventing per-feature IDs.

address clj

(address class-oid object-oid)

(address class-oid object-oid sub-id)

A PostgreSQL object address. sub-id is zero for the object itself and positive for a sub-object such as a table column.

address-key clj

(address-key class-oid object-oid)

Stable structural serialization of a top-level catalog address.

bump-revision-tx clj

(bump-revision-tx db class-oid object-oid)

catalog-entity clj

(catalog-entity db)

catalog-key clj

catalog-version clj

create-object-tx clj

(create-object-tx db
                  {:keys [class-oid oid kind name namespace-oid owner-oid
                          revision legacy-oid? identity-tail]
                   :or {owner-oid 10 revision 1}})

Build an object-row transaction. Namespace may be nil for cluster-global objects; otherwise it must already exist. The two :db.unique/value keys are the atomic stale-reader guard: Datahike rejects duplicates and cannot upsert/merge them as it would :db.unique/identity.

creation-namespace clj

(creation-namespace db entries user-name)

The first existing explicit search_path entry. The implicit pg_catalog entry used for lookup is deliberately not a creation target.

drop-object-tx clj

(drop-object-tx db class-oid object-oid)

first-user-oid clj

identity-key clj

(identity-key class-oid namespace-oid name)

(identity-key class-oid namespace-oid name tail)

Stable structural serialization of a namespace-scoped object identity. tail carries kind-specific identity, notably a routine's argument types.

initialization-tx clj

(initialization-tx legacy-objects next-oid)

initialize-catalog clj

(initialize-catalog txdb legacy-objects next-oid)

Transaction function for an atomic, idempotent version-1 migration. legacy-objects must already have deterministic, collision-free OIDs.

namespace-by-name clj

(namespace-by-name db name)

namespace-by-oid clj

(namespace-by-oid db oid)

object-by-address clj

(object-by-address db class-oid object-oid)

object-by-identity clj

(object-by-identity db class-oid namespace-oid name)

(object-by-identity db class-oid namespace-oid name tail)

objects-by-kind clj

(objects-by-kind db kind)

objects-in-namespace clj

(objects-in-namespace db namespace-oid)

pg-catalog-namespace-oid clj

pg-class-oid clj

pg-namespace-oid clj

pg-proc-oid clj

pg-trigger-oid clj

pg-type-oid clj

public-namespace-oid clj

rename-object-tx clj

(rename-object-tx db class-oid object-oid new-name identity-tail)

reserve-user-oid-tx clj

(reserve-user-oid-tx db)

Reserve one currently-unused user OID with a CAS operation that the caller must transact together with the object creation. Allocation is therefore rolled back with its DDL and naturally chains against a speculative DB.

resolve-search-path clj

(resolve-search-path db entries user-name)

Resolve PostgreSQL search_path entries to existing namespace OIDs. pg_catalog is implicitly searched first unless explicitly positioned. $user contributes a schema only when it exists.

schema clj

Datahike schema for the shared user-object catalog. Address and identity keys use strict unique/value semantics: an attempted duplicate must fail, never upsert or merge two independently-created objects.