Ophir LOJKINE

This was also reported in https://github.com/sqlpage/SQLPage/discussions/695

I think the best option for users is just to launch a `ROLLBACK` before returning the connection to the pool whenever an error occurs. If there was no active transaction,...

We could also add a configuration option to disable the connection pooler completely, which would close the connection after each request, guaranteeing no lingering transactions. This would also be useful...

I implemented automatic rollback of opened transaction before returning a connection to the pool. This way, you cannot get a connection with a half-finished transaction in progress when you start...

I see what you mean... For the first point, there is indeed a performance penalty to running rollback, but it's an order of magnitude lower than discarding the connection. I...

Ok, I'm reopening this :) I changed the implementation, to run a rollback only after an error occurs, and separately added [an optional `sqlpage/on_reset.sql` script](https://github.com/sqlpage/SQLPage/blob/main/configuration.md#connection-cleanup-scripts-on_resetsql) in which you can put...

You are right, thank you! I fixed the docs.

Hi ! Asset sizes are often a limiting factor when integrating large libraries like sql.js. I agree we should include a FTS5 build in our build process, include it in...

I also need that for [good_lp](https://github.com/lovasoa/good_lp). Any pointer on how to fix this ?

You have to run it from the command line. On windows you can use the windows terminal. The output file name (including the extension) is the second argument. https://apps.microsoft.com/detail/9n0dx20hk701?hl=en-US&gl=US