Alexander Prinzhorn

> Is there anything happening in the background that would cause this behavior? There is nothing happening that you don't control/trigger. It's impossible to tell what is happening here with...

See https://nodejs.org/en/guides/simple-profiling for how to profile where the time is spent, I assume one of your queries is super slow. You have `key` indexed, right? > In the meantime swapping...

1. How are you trying to install? Is it simply a `npm i better-sqlite3`? Or globally? 2. How did you install Node.js and npm? Something with your `PATH` is messed...

It might solve your problem in a hacky way but it does not feel like the correct solution since these things are not mutually exclusive. Checking if the directory exists...

https://github.com/WiseLibs/better-sqlite3/issues/1044 https://github.com/WiseLibs/better-sqlite3/issues/1053 Electron 27 should work again

> I am loading sqlite extensions at connection time using the [db.loadExtension()](https://github.com/WiseLibs/better-sqlite3/blob/master/docs/api.md#loadextensionpath-entrypoint---this) API but would rather use the [SQL load_extension() function](https://www.sqlite.org/c3ref/enable_load_extension.html) to load them at runtime. `db.loadExtension()` literally calls `load_extension()`...

Oh, thanks for clarifying, I didn't pay enough attention. Makes sense that you could optionally enable that for a `Database` instance.

> The current example of custom functions is a simple `add2` function which only interacts with the arguments given. Could we get more realistic examples that actually operate on data...

> I guess it would be handy to have something in the docs that demonstrates using the function with data from the database rather than hard-coded args in the query....

I cannot reproduce this with better-sqlite3 8.2.0 and Electron 23.2.1 with the following main.js: ```js const Database = require('better-sqlite3'); const db = new Database(':memory:'); console.log(db.serialize()); ``` What is my repro...