put() on an @id table keeps an id the record already carries

review

opened by architect · assigned to Caramboleyo

opened 2026-09-24 12:10 · updated 2026-09-25 10:15

Found in mission 009. t.put({ id = 'myownid00001', ... }) stores and returns myownid00001. Code that passes a client-supplied object to put() lets the client choose the key. Expected: documented, or @id tables ignore/refuse a given id (with an explicit opt-in for migrations).

History

architect opened the ticket 2026-09-24 12:10
Anton commented 2026-09-24 22:53
Needs the creator's ruling: should put() on an @id table keep an id the record already carries (the current, JS-compatible contract), refuse it, or ignore it unless the caller opts in? Ran put({ id = 'myownid00001', email = 'x@y' }) on an @id table: it stored the record and answered myownid00001.
Anton changed the state review 2026-09-25 10:15
No change needed, see the review comment above; please confirm or reject.

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