better-sqlite3 VS sqlite-gui

In the second video of the series, we are separating routers and adding SQLite, Better SQLite 3, Database to the application to show access to context for performing a simple query and mutation.

If I were charged with this task I'd probably take an actual SQLite DB and write methods to parse data from text files, then process it within SQLite, and serialize it back to the text file when an API method is called or after each processing step. A fresh DB engine, fully re-implemented to match SQLite's API is insane unless you're a prodigy or have a sizable team and will come with numerous downsides. I can recommend https://github.com/WiseLibs/better-sqlite3 and https://github.com/loveencounterflow/dbay

better-sqlite3 is orders of magnitude faster than the async SQLite bindings. We found this to be true when testing SQLite options for Notion's desktop app anyways.

https://github.com/WiseLibs/better-sqlite3#why-should-i-use-...

Better SQLite is a wrapper around the SQLite database engine that provides a number of improvements over the standard SQLite API. One of those benefits is type safety, Better SQLite uses TypeScript to provide type safety for queries, which can help to prevent errors.

better-sqlite3 does the job synchronously

I used better-sqlite3 . It is simple to use as it is synchronous. I don't know if it scales good (at least the docs say it) but works great for my small use cases.

Kent's recommended NodeJS module, `better-sqlite3`, has some very nifty features including the creation of JavaScript user-defined functions[0] that (if I understand this right) can be called from SQLite. Combined with TRIGGERs, I wonder if it might fire a function within the app when an UPDATE/INSERT happens from a different process? (This is me wondering out loud, I don't actually know.)

I also recommend checking out Replicache[1] and alternatives, which may be a better way to handle the networking and database replication so that it doesn't rely on the underlying DB.

[0] https://github.com/WiseLibs/better-sqlite3/blob/HEAD/docs/ap...

DB4S provides only one algorithm based on official SQLite cipher. You can encrypt your database with another in SQLiteStudio or sqlite-gui (I'm an author). Both applications use SQLite3 Multiple Ciphers-library.

Maybe try a GUI program for the Most Widely Deployed and Used Database Engine today. There are numerous other GUI frontends.

https://github.com/little-brother/sqlite-gui/blob/master/res...

The most popular apps areDB4S and SQLiteStudio. If you are planning to run long time queries, then you might encounter with problems by running them in parallel in these tools. To run several queries in a real parallel mode you can use Navicat for SQLite or my sqlite-gui.

Get SQLite editor here: https://github.com/little-brother/sqlite-gui/releases/tag/1.7.8

You can do it by sqlite-gui (I'm author). Open your SQLite database and then go to Main menu > Import > Import via ODBC In a dialog window push ... to run ODBC Administrator, then create DSN for your Access file and after that choose it. Other steps are simple.