Database

Python: also in Node · Go · Rust · Swift · Dart · Java and Kotlin · .NET · C++ · Objective-C

The current writable database.

query, execute and transaction share one convenience connection, created when first needed. connect() creates additional independent connections. A remote supplied at open enables sync(). By default, it also starts automatic synchronization in both directions. Concepts explains the remote and synchronization model.

Operations

Database.clear_quarantine_records

Database.clear_quarantine_records() -> int

Discard full quarantine records and return the number cleared.

Compact safety records remain until authenticated retention permits their retirement.

Database.close

Database.close() -> None

Close all owned connections, then the local store. Repeated calls have the same effect.

close() fails with invalid_state while any owned connection has an active managed transaction. This never closes your Remote.

Database.connect

Database.connect(options: ConnectionOptions | None = None) -> Connection

Create another independent SQLite connection to this database.

Each explicit connection takes its own ConnectionOptions. Closing it leaves the database and siblings usable. Ordinary SQLite locking permits at most one writer at a time.

Database.execute

Database.execute(sql: str, params: Bindings = ()) -> ExecuteResult

Run exactly one state-changing statement on the convenience connection.

The connection reference explains intent rules.

Database.query

Database.query(sql: str, params: Bindings = (), *, engine: QueryEngine = 'sqlite') -> Rows

Run one statement with read execution intent on the convenience connection.

The connection reference explains intent rules.

Database.resolve_conflict

Database.resolve_conflict() -> ConflictResolution

Adopt the authenticated remote revision and replay local work.

The call downloads the revision and stages it durably. It applies the revision while blocking database access and restarting attached connections. It then replays safe pending statements.

The result names transaction IDs in these groups:

• Already published
• Replayed
• Quarantined
• Still pending

Prepared state survives a crash and restart. Production considerations describes replay limits, including FAIL statements and reports after interrupted resolution.

Database.set_sync_policy

Database.set_sync_policy(policy: SyncPolicy) -> DatabaseStatus

Replace the synchronization policy and return the new status. SyncPolicy.manual() disables automatic work but not explicit sync() or resolve_conflict().

Database.status

Database.status() -> DatabaseStatus

Return a typed DatabaseStatus containing these values:

• Current revision
• Pending writes
• Residency and budget
• Connection count
• Synchronization state
• Next delay
• Conflict revision
• Lifecycle

next_sync_in_ms gives the delay until automatic synchronization, in milliseconds. 0 means it is due now. The driver sets it at its last step. It does not count down between steps. It can therefore overstate the remaining delay by the time since that step. It never understates it.

An idle automatic database reports its idle pull interval. None means nothing is scheduled, so waiting on it would wait forever. This occurs when any of these applies:

• The policy is manual.
• A cycle is running.
• A conflict awaits resolution.
• Automatic synchronization failed permanently.
• The database is closed.

When something is scheduled, wait using this field. Do not sleep for a guessed interval instead. On an idle machine, the interval can pass before the work completes.

connection_count includes connections you opened with connect() and the convenience connection created on the database’s first statement. A database with no statements through its convenience connection and no explicit connections reports zero.

Database.sync

Database.sync() -> SyncResult

Synchronize once with the remote.

If the device has local writes to publish, this call publishes them. Otherwise, it checks the remote head and pulls a newer revision if one exists. A failed attempt keeps its prepared writes for a later attempt, and that retry can leave newer writes pending.

It returns exactly one result: UpToDate, Pushed, Pulled or Conflict. A Conflict is returned as a value without raising an exception. Automatic synchronization stays paused in that state until resolve_conflict runs. Without a remote, this call fails with remote_required.

Database.transaction

Database.transaction(*, mode: TransactionMode = 'immediate') -> _Transaction

Begin one managed transaction on the convenience connection. The default mode is immediate.

Which engine answers a read

Use query to choose the engine. Default reads use SQLite. Select DuckDB with engine="duckdb". Only these two engines are supported. An invalid selection fails instead of selecting the default.

The packaged Python SDK supports SQLite and DuckDB.

The native SDK loads DuckDB when you first request an analytical read. OpenOptions.analytical_engine selects the library for one database or snapshot. It takes priority over POTLUCKDB_DUCKDB_LIBRARY, package discovery where available, and the platform’s library search. An explicit selection, including an empty string, never uses a fallback.

See analytics engine installation for your platform. Without an implicit library, the read fails with analytical_engine_unavailable. If an explicit library cannot load, the read reports its loader error.

Install it with pip install potluckdb-analytics, which resolves the wheel built for this platform.

DuckDB rejects the named binding forms :name and @name. Both engines accept $name and positional ? bindings. Booleans bind as INTEGER 0/1 on both. IS therefore asks the same question on either engine, unlike a DuckDB BOOLEAN binding.

Bare table names read the database’s main schema. Qualifiers such as temp. are not seen. For table names ending in .csv, .parquet or .json, use potluckdb_scan('name'). DuckDB otherwise treats those names as files.

NUMERIC and DECIMAL columns read as doubles. A value that a double cannot hold exactly fails the query instead of arriving rounded.

A storage failure during an analytical read reports analytical_engine_error, with the failure named in its message. The same query succeeds when storage answers.

Either engine runs one read per query. The analytical engine reads a snapshot of the same data through its own in-memory database. A statement sent to this engine therefore cannot change the stored data.

An engine can remain for the session’s lifetime. Changing its settings or catalog would change later queries on that session. Only SELECT and EXPLAIN are accepted. CREATE, SET, ATTACH, PREPARE and EXPLAIN ANALYZE are refused. EXPLAIN ANALYZE is refused because it executes the explained statement.

Use execute for writes to the stored data.