v10.0.6 — canonical Sakila schema

What's new

Regenerated sakila.db to align with the canonical SQLite Sakila DDL. Closes #2.

• Single-column integer primary keys are now declared inline as INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL (was: numeric / int / SMALLINT with a separate PRIMARY KEY (...) clause).
• last_update columns gain NOT NULL DEFAULT CURRENT_TIMESTAMP.
• sqlite_sequence is seeded so future AUTOINCREMENT inserts continue from the existing max id.
• Composite-PK tables (film_actor, film_category) and film_text are intentionally untouched.

The user-visible effect: actor.actor_id is now returned with wire type integer over rqlite's HTTP API. Previously it came back as numeric, which clients like gorqlite decode as float64 instead of int64 — that mismatch was the issue that surfaced the bug.

Try it

docker pull sakiladb/rqlite:10
docker run -p 4001:4001 -p 4002:4002 \
    --add-host rqlite1:127.0.0.1 \
    -d sakiladb/rqlite:10

curl -s -u sakila:p_ssW0rd \
     'http://localhost:4001/db/query?level=strong&q=SELECT+actor_id+FROM+actor+LIMIT+1'
# {"results":[{"columns":["actor_id"],"types":["integer"], ...
#                                     ^^^^^^^^^ was "numeric"

Reproducibility

The schema transformation is committed as tools/regenerate-sakila.sh so the change can be reproduced from source rather than treated as an opaque blob swap.

Image tags

• sakiladb/rqlite:latest
• sakiladb/rqlite:10

Both signed via cosign keyless OIDC.

Known follow-ups

• #5 — customer.active default 'Y' is inconsistent with the customer_list view's numeric comparison. Pre-existing schema drift inherited from the upstream jOOQ Sakila, not introduced by this release.