better-sqlite3 | The fastest and simplest library for SQLite3 in Node.js | Database library

Just update all the data because if you want to update only one target, the process is bigger than updating all the data

@zac-rougeau In my opinion for back-end code, you have to use res.send('hello') instead of res.get(). You can test your back-end APIs with some tools like Postman, Insomnia.

Here, I've written very simple get API which returns hello (like your case) string and I've tested this get API with Postman.

Code

Postman

Likewise, you can test your API with postman and if you get hello in your postman as a response, then you have to debug your front-end code.

Also, In your front-end code, you're pointing port 3000 in axios.get() method. Actually, it's 8100 (in your case). Could you please change that to proper back-end port and check once again ?

I believe I had this error once, the simple fix is replacing the icon as the one I had was somehow corrupted. Just re-create the .ico icon and add it.

Funny how things break on their own and it's not your fault.

Here's my set up start to finish.

First lets address a basic set up for just running the DB with NestJs, dotenv, and config files. Obviously we've moved away from ormconfig.json which doesn't support .env.

app.module.ts

Solved the issue, I was using an outdated version of node as I was using node v16.13.2 so I tried switching to the most latest version (v17.4.0 as of now) and it works like a charm now.

Here's the answer from the SQLite forums. Essentially this is a combination of how the query planner handles IN literals and what cost my virtual table estimates. That means I'm running into the exact moment when the query planner makes a different decision.

SQLite NGQP is a cost based query planner. The IN () operator with a list of literal values gets implemented as a kind of temporary table; sometimes SQLite decides to create an index and do lookups, other times it decides to use that table as the outermost loop of the query.

EXPLAIN QUERY PLAN should show that in a more concise manner.

If compiled in DEBUG mode mith WHERETRACE enabled, the .wheretrace command will show how SQLite NGQP reaches its plan. Essential input is the return values from the xBestIndex method of your virtual table, especially the "number of rows" and the "estimated cost". It is paramount to deliver accurate estimates. Cost should reflect processing cost relative to SQLite native tables.

Note that you can name the IN table by making it a CTE and CROSS JOIN to force the query plan that works fast.

https://sqlite.org/forum/forumpost/a3d68ed8b40cf583?t=h

The workaround I use is json_each and serialize the array of integers into a JSON string. In my particular use-case this has some other benefits as well (e.g. I can bind a single parameter and re-use the query with any number of IDs), so I don't mind doing that:

You would have to force clean your npm cache and remove your node_modules and reinstall them again to compile them against a new node version, for the same you may use the following commands in your Console / Shell:

client.on is indeed not a function. It is a listener.

Anyways your problem seems to be on line 123:

Many node modules are just JavaScript and are portable across systems. Some, however, contain native compiled code. The SQLite library you are using is not 'pure JavaScript' and relies on a binary.

When you npm install-ed it installed a binary for the system you were using at that time, for example, you were on a Mac. The better_sqlite3.node file was for that specific operating system.

You then opened this project on a different computer but also copied over the node_modules directory. Just like how you can't run .app files on Windows or (usually) .exe on Linux, this binary is not compatible with your OS. Removing and then re-installing the SQLite library will install a Windows-compatible binary.

Since your project is in a OneDrive folder, it might be that you are switching between operating systems. That could make this process tedious. One workaround would be to install the SQLite module globally, but that has some drawbacks.

require() will look not just through the current directory, but also recursively directories above it (eg ...\OneDrive\Coding\sil, then ...\OneDrive\Coding, then ...\OneDrive), before checking the global directory.