sqlite-viewer VS better-sqlite3

Now open the http://127.0.0.1:8000/, you will see the following output: You can also use sqlite3 command line tool or SQL Viewer tool in order to inspect changes in your database.

Just for fun, I threw the db.sqlite3 database on testing site, https://inloop.github.io/sqlite-viewer/, to see if the data is still valid and it is, I just need to redirect django to point to the local sqlite3 database.

Now have a look in that database ( https://inloop.github.io/sqlite-viewer/ ) and compare it to your external drive file paths. Maybe the drive has a different name…?

So, try using a tool that can read SQLite databases, like https://inloop.github.io/sqlite-viewer/ or https://sqlitebrowser.org/

sqlite-viewer - View SQLite file online

The History file is an SQLite database. You can see its contents on this webpage: http://inloop.github.io/sqlite-viewer/

SQLite Viewer - Online .db, .sqlite3, etc. File Viewer. Open Source. Website.

I was able to open them with this tool: https://github.com/inloop/sqlite-viewer

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...