Replies: 1 comment 2 replies
-
Hi @linonetwo my experiments in this area have focussed on the browser, not Node.js. In terms of the size of the binaries, SQLite offers a distribution of the WASM build that is 782KB compressed: https://sqlite.org/download.html I downloaded that bundle, and then used a simple HTTP server in the root of the extracted ZIP and ran the following demo: http://127.0.0.1:8080/demo-123.html On my system, this demo used sqlite3.js, which weighs in at 369KB. So I think that's OK for an optional plugin. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Problem
sqlite binary size
SQLite nodejs binding is 23M+ (Compared to tiddlywiki core + all core plugins = 19.7M). And every wiki will have a copy of this plugin (unless it becomes part of the core? This is not very possible, because it relies on 1 or 2 npm packages and their deps and deps of deps).
sqlite .db file size
My wiki is 40M, so sqlite's
.db
file will be at least 40M+. I won't want this database file sync to Tiddlyhost or GitHub.Possible Solution
$tw.utils.Sqlite
if nodejs wiki is running in TidGi. If other tw launcher apps want to do the same, I can point out the code lines, and give a hind..db
file is not expected to be human readable, I consider it to be a cache that is only used by programs. So I put it in the appData folder (/Users/linonetwo/Library/Application Support/TidGi
on MacOS), instead of in the wiki folder.Seems I already mentioned this in #7302 (comment)
Beta Was this translation helpful? Give feedback.
All reactions