Jussi Saurio f48165eb72 fix/vdbe: reset op_transaction state properly ...

essentially after the first runthrough of `op_transaction` per a
given `ProgramState`, we weren't resetting the instruction state
to `Start´ at all, which means we didn't do any transaction state
checking/updating.

PR includes a rust bindings regression test that used to panic before
this change, and I bet it also fixes this issue in turso-go:

https://github.com/tursodatabase/turso-go/issues/28

2025-10-02 08:40:41 +03:00

..

builder.rs

fix self-insert bug

2025-09-29 17:18:19 -04:00

execute.rs

fix/vdbe: reset op_transaction state properly

2025-10-02 08:40:41 +03:00

explain.rs

Merge remote-tracking branch 'origin/main' into cdc_fail_autoincrement

2025-09-24 18:06:02 +05:30

insn.rs

core: change page idx type from usize to i64

2025-09-29 18:38:43 +02:00

likeop.rs

Rename OwnedValue -> Value

2025-05-15 09:59:46 +03:00

metrics.rs

add metrics and implement the .stats command

2025-08-18 09:11:06 -05:00

mod.rs

core/vdbe: Don't clear parameters in Statement::reset()

2025-09-30 20:22:09 +03:00

sorter.rs

core/vdbe: Wrap SortedChunk::total_bytes_read with AtomicUsize

2025-09-27 14:35:31 +03:00