Alexander Prinzhorn

> 4\. check if the bind this logic should be called again is done by looking if the array instance has changed, which it has due to the spread/slice I...

For the time being I'm using a second `readonly` connection to query the data inside the user-defined function. Works as expected and is only a little awkward. So if there...

Thanks for the reply. > For the same reason as in #203, it's currently disabled. Reading is [not disabled anymore](https://github.com/JoshuaWise/better-sqlite3/issues/203#issuecomment-456534827), #203 is open because the writing part is still open....

For future reference: I don't think SQLite itself has any issues with doing what is asked here > An application-defined function is permitted to call other SQLite interfaces. However, such...

I'm not Joshua, but I want to give my opinion. > It'd be a shame to see the competition win out This is unfortunately the mindset that keeps burning people...

@bobOnGitHub fair enough

So much for "Development of this module is sponsored by MapBox." https://github.com/mapbox/node-sqlite3/issues/1292 https://kewde.github.io/sqlite --- > In fact, I'm not using `better-sqlite3` for anything in my life right now. However, since...

> Please try re-compiling or re-installing the module (for instance, using `npm rebuild`or`npm install` I assume this didn't fix it? You are probably copying `node_modules` around.

I'm sure the solution is in here somewhere: https://github.com/JoshuaWise/better-sqlite3/search?q=The+module+was+compiled+against+a+different+Node.js+version&type=issues This is not an issue with better-sqlite3, you must be doing something wrong with how you install/build your packages.

I assume the wrong prebuilds are currently installed (instead of failing the prebuild), see https://github.com/JoshuaWise/better-sqlite3/pull/800