Account and actor database queries.
Provides CRUD operations for the account and actor tables. For v1, every account has exactly one actor (1:1).
14 declarations
auth/account_queries.ts view source
AdminAccountListOptions Options for query_admin_account_list.
limitMax accounts to return. Defaults to ADMIN_ACCOUNT_LIST_DEFAULT_LIMIT
when omitted; pass null explicitly to disable the limit (unbounded
fetch — for trusted internal callers / scripts; the RPC schema bounds
wire callers to [1, ADMIN_ACCOUNT_LIST_LIMIT_MAX]).
number | nulloffsetPagination offset. Defaults to 0.
number | nullauth/account_queries.ts view source
(deps: QueryDeps, email: string): Promise<Account | undefined> Find an account by email (case-insensitive).
depsemailstringPromise<Account | undefined> auth/account_queries.ts view source
(deps: QueryDeps, id: string): Promise<Account | undefined> Find an account by id.
depsidstringPromise<Account | undefined> auth/account_queries.ts view source
(deps: QueryDeps, username: string): Promise<Account | undefined> Find an account by username (case-insensitive).
depsusernamestringPromise<Account | undefined> auth/account_queries.ts view source
(deps: QueryDeps, input: string): Promise<Account | undefined> Find an account by username or email.
If the input contains @, tries email lookup first then username.
Otherwise tries username first then email. This supports a single
login field that accepts either format.
depsquery dependencies
inputusername or email address
stringPromise<Account | undefined> the matching account, or undefined
auth/account_queries.ts view source
(deps: QueryDeps): Promise<boolean> Check if any account exists.
depsPromise<boolean> auth/account_queries.ts view source
(deps: QueryDeps, id: string): Promise<Actor | undefined> Find an actor by id.
depsidstringPromise<Actor | undefined> auth/account_queries.ts view source
(deps: QueryDeps, account_id: string): Promise<Actor[]> List every actor on an account, ordered by created_at.
Used by resolve_acting_actor to resolve the acting actor for a
request: 1 actor picks transparently, multiple require an explicit
acting field on the request payload. For lookups by id, use
query_actor_by_id instead.
depsaccount_idstringPromise<Actor[]> auth/account_queries.ts view source
(deps: QueryDeps, options?: AdminAccountListOptions | undefined): Promise<{ account: { id: string & $brand<"Uuid">; username: string; ... 4 more ...; updated_by: (string & $brand<...>) | null; }; actor: { ...; } | null; role_grants: { ...; }[]; pending_offers: { ...; }[]; }[]> List accounts with their actors, active role_grants, and pending inbound role_grant offers for admin display.
Pages the accounts query (one round-trip), then fans out three parallel
lookups scoped to the page's account_ids (one round-trip). The role_grants
and offers queries use a subquery on actor.account_id so the page bound
pushes through to the DB without round-tripping actor.ids back to the
application. Pending offers surface the "offer pending — awaiting
acceptance" UX; message is intentionally excluded (cross-admin
visibility of grantor notes would expand beyond what the audit log
discloses).
depsquery dependencies
options?optional {limit, offset}. Default limit is
ADMIN_ACCOUNT_LIST_DEFAULT_LIMIT; pass limit: null to disable.
AdminAccountListOptions | undefinedPromise<{ account: { id: string & $brand<"Uuid">; username: string; email: string | null; email_verified: boolean; created_at: string; updated_at: string; updated_by: (string & $brand<"Uuid">) | null; }; actor: { ...; } | null; role_grants: { ...; }[]; pending_offers: { ...; }[]; }[]> admin account entries sorted by creation date (oldest first)
auth/account_queries.ts view source
(deps: QueryDeps, input: CreateAccountInput): Promise<Account> Create a new account.
depsquery dependencies
inputthe account fields
Promise<Account> the created account
auth/account_queries.ts view source
(deps: QueryDeps, input: CreateAccountInput): Promise<{ account: Account; actor: Actor; }> Create an account and its actor in a single operation.
For v1, every account gets exactly one actor with the same name as the username.
depsquery dependencies
inputthe account fields
Promise<{ account: Account; actor: Actor; }> the created account and actor
auth/account_queries.ts view source
(deps: QueryDeps, account_id: string, name: string): Promise<Actor> Create a new actor for an account.
depsquery dependencies
account_idthe owning account
stringnamedisplay name (defaults to account username)
stringPromise<Actor> the created actor
auth/account_queries.ts view source
(deps: QueryDeps, id: string): Promise<boolean> Delete an account. Cascades to actors, role_grants, sessions, and tokens.
depsidstringPromise<boolean> auth/account_queries.ts view source
(deps: QueryDeps, id: string, password_hash: string, updated_by: string | null, expected_hash: string): Promise<boolean> Update the password hash for an account, conditional on the current
stored hash matching expected_hash — the verify-write atomic guard.
The condition closes the race where two concurrent password changes both verify against the pre-update hash (loaded by the authorization phase outside the route's transaction) and would otherwise both UPDATE, silently clobbering whichever lands first. With the conditional WHERE, the second UPDATE matches zero rows; the route reads the boolean return and surfaces 401 instead of pretending success.
Pass the same hash the verify ran against — typically
ctx.account.password_hash from the request context.
depsidstringpassword_hashstringupdated_bystring | nullexpected_hashstringPromise<boolean> true if the row was updated, false if expected_hash no
longer matched (concurrent change won — caller should treat as a
stale-credential failure).