Releases

This is a reverse chronological summary of TinyJoin releases and their public compatibility boundaries.

v0.0.6

This release is being prepared locally and has not yet been published.

Persistent storage breaks compatibility with v0.0.5. The npm v0.0.5 release uses page format 1; v0.0.6 uses page format 2. Opening a v0.0.5 database with v0.0.6 fails with UNSUPPORTED_PAGE. There is no automatic migration, and changing the OPFS name does not copy existing data.

• For data that can be reconstructed, use a new OPFS namespace, for example change opfs://my-app-v1 to opfs://my-app-v2, and rebuild the database. The old namespace remains intact.
• To retain existing data, export the application's known tables using a client pinned to tinyjoin@0.0.5 before upgrading. Create the schema in a new namespace with v0.0.6, import rows with parameterized statements, and verify the data before retiring the old database. TinyJoin does not yet provide a general database export or migration API.
• New apps generated by create-tinyjoin v0.0.7 target tinyjoin@^0.0.6 and use a -db-v2 storage name. Updating the generator does not migrate applications it generated previously.

This release also makes predicate and assignment type validation consistent across reads and writes, compares heterogeneous JSON values consistently, and bounds shared parameter-graph traversal and expanded SQL bindings before copying values. Append-only transactions now validate new row statements incrementally, including unique-index checks; mixed writes retain complete staged write-set validation.

Selective multi-table joins now use their actual comparison count rather than a worst-case Cartesian estimate. Scan, build-row, result, memory, and shared script-work limits remain in force.

Duplicate output names in simple projections and RETURNING now fail consistently with INVALID_QUERY before execution. LIMIT and OFFSET reject nonnumeric parameter values consistently in ordinary, aggregate, and join queries, including JSON objects shaped like internal prepared placeholders.

Persistent Clients now coordinate automatically across tabs and within a page. One elected Worker owns the database; operations, prepared statements, and notifications follow it through handover. Callback transactions exclude other Clients for their duration. In-flight operations interrupted by owner loss reject without automatic replay, and incompatible releases reject explicitly.

The optional tinyjoin/vite build plugin precaches a complete production application, including lazy Worker, OPFS, and WASM assets. New starter apps enable it by default. Updates wait for old controlled tabs to close; existing service workers can use its generated manifest and helper instead. See the offline guide.

v0.0.5

This release establishes TinyJoin as a standalone, SQL-first browser database package.

• create() opens the packaged dedicated Worker and WebAssembly engine with no application Worker boilerplate.
• Memory and persistent OPFS databases use one bounded page-native engine.
• The JavaScript client provides parameterized queries, atomic scripts, callback transactions, reusable prepared statements, and table-level change subscriptions.
• Typed tables support primary keys, maintained secondary and unique indexes, bounded schema additions, aggregates, and left-deep inner and left joins.
• Results use a familiar rows, fields, affectedRows, command, and rowCount shape, with TinyJoin revision and changed-table metadata.
• The published package includes its runtime, Worker, WASM, declarations, compatibility guide, README, release notes, and agent guidance.

TinyJoin remains experimental and deliberately smaller than PostgreSQL. This release does not include a PostgreSQL server or wire protocol, hosted service, remote replication, or offline-write synchronization.