js-bao 0.12.0-alpha.0 → 0.12.0-alpha.2

package/README.md

@@ -1559,6 +1559,39 @@ See the `examples/` directory for complete working examples:
 Changes to the on-disk behaviour of `js-bao/cloudflare/do` (`DurableObjectEngine`)
 that a store's owner can observe. Newest first.
 
+- **New stores get a record-first StringSet table** (#3877). A store the
+  engine creates declares `stringset_index` with `UNIQUE(_type, _record_id,
+  field, value)` (record-first) instead of `UNIQUE(_type, field, _record_id,
+  value)` (field-first). That key serves every statement
+  `idx_ss_type_record_field` served, so on a record-first table the index is
+  retired: the engine never builds it there and removes any copy on open, by
+  definition and under any name, and a StringSet value costs three rows written
+  instead of four. A unique key cannot be altered in place, so an existing store
+  keeps the shape it has, both member indexes included; both shapes are
+  supported and return the same results, in the same value order.
+  `engine.memberTableShape` answers the stored shape, and the new export
+  `DURABLE_OBJECT_SCHEMA_OPTIONS` is the schema options a new store is created
+  with. `JsonSchemaDDL`'s output for every existing option is unchanged, so
+  client stores keep the field-first table. On the platform, a large document
+  converts at its next bulk-load ingest and a plain document at its next
+  projection rebuild; databases keep their shape. `rebuildMemberTable` is
+  `@internal`, used only by that rebuild. Rollback floor: do not roll back past
+  the last release before this one while an ingest is running; a store opened
+  by an older release re-creates `idx_ss_type_record_field`, and this release
+  removes it again on its next open. See also the `_indexes.created_at` entry
+  below.
+- **`idx_records_type` is retired** (#3876). The primary key `(_type, _id)`
+  already leads with `_type`, so a new store no longer builds the index and an
+  existing one loses it on its next open, removed by definition under any name
+  (an ingest-suffixed copy included); a record insert writes one row fewer.
+  Dropping a field index or a unique constraint keeps the physical index while
+  another registration still maps to the same definition, under the name it
+  already has; a later index whose canonical name that kept index holds is
+  created as `<canonical name>_2` (or the next free suffix). Duplicate copies of a
+  definition the engine owns (base, retired or registered) collapse to one on
+  open; an index created outside the engine is never dropped. Index definitions
+  now compare with quoted literals verbatim, so `WHERE _type = 'a b'` and
+  `WHERE _type = 'ab'` are different indexes. Client stores are unchanged.
 - **`_indexes.created_at` reports the first registration** (#3875). Re-registering
   a field index whose `field_type` and `is_unique` are unchanged no longer
   rewrites its `_indexes` row: it writes no row, and `created_at` keeps the time