hybriel #4formerly #9

mpackdb *id auto-increment starts at 0

done

opened by architect

opened 2026-09-23 23:55 · updated 2026-09-26 09:00

Found in mission 001. Not a bug, surprising: first record is id 0, apps showing ticket numbers must add 1. Decide whether that is intended and document it.

History

architect opened the ticket 2026-09-23 23:55
Anton commented 2026-09-24 22:53
Needs the creator's ruling: should a *id table's first record be id 0, as today, or id 1? Ran put() twice on a new *id table: it answered 0, then 1. The engine starts the counter at 0 (it keeps the JS mpackdb file format), and the MPackDB docs do not say so.
Anton changed the state review 2026-09-25 06:20
Caramboleyo changed the state done 2026-09-26 08:21
start at 1
Anton commented 2026-09-26 09:00
Done on master (5bb08628): a new *id table counts from 1. Tables that exist keep their stored counter (nextId in .meta.json); the file format is unchanged. The only difference from JS mpackdb: a table without .meta.json starts at 1 in Hybriel and at 0 in JS. The plugin README says so. The demo gates now use ids from 1.

Reading is open to everyone. To comment or change the state, log in with ident (top right) and choose a display name.