The served page cache and fill queue, in the object's own SQL (not Drupal's cache_page): the
hit path must be readable by JS alone, without booting PHP.
The tables are WITHOUT ROWID: a text key in a rowid table gets its own unique index and an
insert charges 2 rows instead of 1 (measured on ctx.storage.sql). Nothing consumes a rowid,
and IF NOT EXISTS leaves an existing site's rowid tables alone (not worth a rebuild).
The served page cache and fill queue, in the object's own SQL (not Drupal's
cache_page): the hit path must be readable by JS alone, without booting PHP.The tables are
WITHOUT ROWID: a text key in a rowid table gets its own unique index and an insert charges 2 rows instead of 1 (measured onctx.storage.sql). Nothing consumes a rowid, andIF NOT EXISTSleaves an existing site's rowid tables alone (not worth a rebuild).