Cross file internal link internals (db.sqlite3)

When running in Node.js, OurBigBook dumps the IDs of all processed files to a _out/db.sqlite3 file in the _out directory, and then reads from that file when IDs are needed.

When converting under a directory that contains ourbigbook.json, _out/db.sqlite3 is placed inside the same directory as the ourbigbook.json file.

If there is no ourbigbook.json in parent directories, then _out/db.sqlite3 is placed in the current working directory.

These follows the principles described at: the current working directory does not matter when there is a ourbigbook.json.

db.sqlite3 is not created or used when handling input from stdin.

When running in the browser, the same JavaScript API will send queries to the server instead of a local SQLite database.

To inspect the ID database to debug it, you can use:

It is often useful to dump a single table, e.g. to dump the ids table:and one particularly important query is to dump a list of all known IDs:

You can force ourbigbook to not use the ID database with the --no-db command line option