Jussi Saurio a66b56678d Merge 'Reprepare Statements when Schema changes' from Pedro Muniz ...

Closes #1967
To support this I had to change how we did `epilogue` similarly to how
SQLite does it. SQLIte first declares a `beginWriteOperation` when some
statement is going to necessitate a Write Transaction. And as we now
need to pass the current schema cookie to `epilogue` it was easier to
call epilogue only in one location (like we do with prologue), and just
have each statement declare their intentions separately. This allows us
to not have to pass the Schema around just to do the epilogue. I believe
this is something that @jussisaurio would be interested in.
~Also had to disable the MVCC test, as it was extremely buggy for me.~
Just disabled reprepare statements for MVCC

Reviewed-by: Jussi Saurio <jussi.saurio@gmail.com>

Closes #2214

2025-08-05 00:01:14 +03:00

..

mod.rs

Do not rollback in TxError

2025-07-18 01:11:51 -03:00

test_btree.rs

convert must_use compile warnings to unused_variables to track locations where we need to refactor in the future

2025-07-28 16:09:26 -03:00

test_multi_thread.rs

workaround the fact that to reparse schema we have to avoid falling into a reprepared statement loop

2025-08-04 12:32:34 -03:00

test_read_path.rs

fix tests

2025-08-04 13:08:30 -03:00

test_transactions.rs

workaround the fact that to reparse schema we have to avoid falling into a reprepared statement loop

2025-08-04 12:32:34 -03:00

test_write_path.rs

Remove assert for !NO_LOCK_HELD, properly handle writing header if reset

2025-07-30 14:08:51 +03:00