aboutsummaryrefslogtreecommitdiff
path: root/ext/wasm/api
Commit message (Collapse)AuthorAge
* Remove unnecessary "www." prefixes on domain names in URLs.drh2025-04-10
| | | FossilOrigin-Name: 20acd630b91609725794ce84f9eda01d5f3c898407f0948264830851d25ccaa6
* Fix a long-standing filename digest computation bug in the OPFS SAHPool VFS ↵stephan2025-03-16
|\ | | | | | | | | which caused all VFS-stored filenames to have a digest value of 0. See [/forumpost/042d53c928382021] and for full details. FossilOrigin-Name: 493cbe74504e8eb1ca8f2edf49fdab6bebc7fe36ffab06932a4b8c5a4eea86cd
| * Minor doc corrections for the sahpool-digest fix and merge in current trunk.stephan2025-03-14
| |\ | |/ |/| FossilOrigin-Name: 500f2e6ec74b4c0e4ac0365ba4e0d81ed6df8dd09dc0f8af65d294c3453f8865
| * Merge trunk into the sahpool-digest branch.stephan2025-02-26
| |\ | | | | | | FossilOrigin-Name: fc1eeb7d1f2880907b0fe71a8c572dd7cd74a5d65ec0177332976ad2f8c2b216
| * | More work on the sahpool digest fix. New/fixed versions can read legacy (no ↵stephan2025-02-26
| | | | | | | | | | | | | | | digest) files but the reverse is only possible in limited circumstances (when files originated from a legacy version). The burning question is whether the real fix would be to remove this digest check altogether, as it only applies in a very limited context, and the fact that it was broken for some 18 months unnoticed suggests that its value might not be worth the CPU cycles. FossilOrigin-Name: 0df62b776c68bebb0e187b353b6f29b0a41a29f0a1c8d6728fa6b9f7ce0d13f7
| * | Add a test app to assist in validating the SAHPool digest calculation fix.stephan2025-02-03
| | | | | | | | | FossilOrigin-Name: a1e304b8020025cc73a658bd8c7697d59b4f3ad96cac0a3e36553a3207d13dc6
| * | Initial work on a fix for the SAHPool VFS's effectively-no-op digest ↵stephan2025-02-03
| | | | | | | | | | | | | | | calculation, as reported in [https://github.com/sqlite/sqlite-wasm/issues/97|ticket #97 of the downstream npm subproject]. This requires more testing alongside databases created before this version to ensure that it's backwards-compatible. FossilOrigin-Name: 9234c33f92d92bfddc6211c9c587f1072e70837c0ffe1416ef7d84d59bacd364
* | | Use SQLITE_EXTRA_INIT_MUTEXED instead of SQLITE_EXTRA_INIT for the ↵stephan2025-03-01
| | | | | | | | | | | | | | | SQLITE_WASM_EXTRA_INIT feature, as suggested in [forum:14183b98fc0b1dea|forum post 14183b98fc0b1dea]. This doesn't make a functional difference now - this is in the name of future-proofing against eventual threading support in wasm. FossilOrigin-Name: 46479c2e30b9676e0fa8da117ba67f673671fb340c9bea38ece19a1b2371a57b
* | | Approximately 100 typo corrections spanning the whole tree, submitted via ↵stephan2025-02-27
| |/ |/| | | | | | | [forum:0db9827f0464bc33|forum post 0db9827f0464bc33] and individually audited and verified. Affects only code comments, innocuous test strings, error message text in tool (not library) code, and configure-level help text. FossilOrigin-Name: f50c21484d3cac73589da0376c423de39ae8b842218105786c5aa3726e4dcaed
* | Approximately 50 typo fixes, spanning the whole tree, contributed via ↵stephan2025-02-25
| | | | | | | | | | [forum:006c8fa165083ac3|forum post 006c8fa165083ac3] and individually checked for correctness. Affects only code comments, docs, and a single line of debug output in a test app. FossilOrigin-Name: af928818a030924060ee0762431dae0f16d53a62f4e1132754d052eb9c621ac2
* | Add the pause/unpause capability to the opfs-sahpool VFS, as discussed in ↵stephan2025-02-20
|\ \ | | | | | | | | | | | | [forum:fe8cdb8431c|forum thread fe8cdb8431c]. Summary: this gives clients a way to eke some degree of multi-page/tab/Worker concurrency out of this VFS but requires that coordination to be implemented client-side, e.g. via a SharedWorker or WebLocks. FossilOrigin-Name: b5dbd521951e129b4dec69f191a872500dbf387b34a8479ad58b053ffcccbab9
| * | Minor cleanups in the opfs-sahpool pause/unpause API demo.stephan2025-01-31
| | | | | | | | | FossilOrigin-Name: e205cdc468e02eefdeb8d391d921aa2d4d28a8b7b87036d6d937a9928261a413
| * | Cleanups in the opfs-sahpool VFS pause/unpause feature and its tests.stephan2025-01-31
| | | | | | | | | FossilOrigin-Name: 184ba37702f63196deca91d273e798ca895fbb301938e6264bc82815a4e33149
| * | Merge trunk into opfs-sahpool-pause branch.stephan2025-01-31
| |\ \ | | | | | | | | FossilOrigin-Name: 775a547eca2b0b3dbb6c03990236128a095cc34d28caec44b9a5072510c75b63
| * | | Simplify how OpfsSAHPoolUtil.unpauseVfs()'s returned promise is handled.stephan2025-01-29
| | | | | | | | | | | | FossilOrigin-Name: d651b8da5a84cd54d71f15bd34e4db685674ef73f26f5cc26b7af5321a2ec05e
| * | | Add experimental support to pause/unpause an SAHPool OPFS VFS, as discussed ↵stephan2025-01-29
| | | | | | | | | | | | | | | | | | | | in [forum:fe8cdb8431c32455|forum post fe8cdb8431c32455], the intent being enable a page to relinquish, perhaps temporarily, the VFS such that the VFS's storage can be accessed by another page/tab. FossilOrigin-Name: 1d2683fe9e4be01c3137e750900f54d287e7d96185e66924d24b50f4647e7ef1
* | | | wasm: when building in -O0 mode (typical dev mode), use -sASSERTIONS=2, else ↵stephan2025-02-09
| | | | | | | | | | | | | | | | | | | | -sASSERTIONS=0, in response [https://github.com/emscripten-core/emscripten/pull/23629/commits/7e3e35cbff9c5688eacb3cddc5045f872d744efd|Emscripten checkin 7e3e35cbff9], which adds assertions to check for the condition reported in [https://github.com/emscripten-core/emscripten/issues/23420|Emscripten ticket 23420]. Update some unrelated JS-side internal docs. FossilOrigin-Name: 1f554610ba5d9d474ec4570bb7ca09125fd2cdfb4976530a4227cc6ebdf3a962
* | | | JS: add a mechanism to the Worker1 exec API to fetch the ↵stephan2025-02-09
| | | | | | | | | | | | | | | | | | | | last_insert_rowid(), as requested in [forum:56bc35390183f5d5|forum post 56bc353901]. FossilOrigin-Name: c22c48360756b1c7e2f5a9c01aff799bc188e100d364931de0dc3686e5de57a9
* | | | Rework [76c8435a] to eliminate automatic JS-to-WASM function conversions of ↵stephan2025-02-03
| |_|/ |/| | | | | | | | | | | sqlite3_set_auxdata() destructors because it can leads to leaks on every call of a UDF. This feature never worked before [76c8435a] but fixing it was ill-conceived because of the memory leakage it introduces. WASM function pointers can still be used as destructors in this context. FossilOrigin-Name: 3fb993af0caf041da934cea29c039b27c468be0b75bce1537a6425767cf9bf8d
* | | Add a more complete test for [76c8435a] and add some commentary about (A) ↵stephan2025-02-03
| | | | | | | | | | | | | | | the inability to automatically clean up automatically-generated WASM proxy functions for sqlite3_set_auxdata() destructors and (B) how to deal with (A) to avoid leaking WASM proxy functions. FossilOrigin-Name: d693c2dddbd10a2e0b77893b04b11502e30b768f1b06814105f7f35172845fb9
* | | Correct the FuncPtrAdapter signature for the JS binding of ↵stephan2025-02-03
| | | | | | | | | | | | | | | sqlite3_set_auxdata(). Reported in [https://github.com/sqlite/sqlite-wasm/issues/92|the npm subproject, ticket #92]. FossilOrigin-Name: 76c8435a5f390001038b8ee94322ff478c9d5f29501ed1c5891c952a41e377aa
* | | Expose the new SQLITE_DBCONFIG_ENABLE_ATTACH_CREATE/WRITE and ↵stephan2025-01-31
| |/ |/| | | | | | | SQLITE_DBCONFIG_ENABLE_COMMENTS (from [325e547a21955]) to JS/WASM. FossilOrigin-Name: 8da1a9af66f905c683e9c3445d609b5c0e11ac912be192c468ddd79f237837f4
* | Minor wasm-specific doc touchups.stephan2025-01-31
|/ | | FossilOrigin-Name: 56b618da9073db8b8d5dafa177a3c9e4c4d927bf512e14b0e6d23937f91ce4cf
* Replace use of Emscripten's Module.postRun() with a custom callback so that ↵stephan2025-01-16
| | | | | we get consistent library init timing with both Emscripten 3.1.x and 4.0.x. Details and discussion are in [https://github.com/emscripten-core/emscripten/issues/23420|Emscripten ticket #23420]. FossilOrigin-Name: 4863a70ac61ff6f868429f16f0141484ea98f973fde1a9aff879252d0f1dbb6b
* Work around [https://github.com/emscripten-core/emscripten/issues/23420|a ↵stephan2025-01-15
| | | | | behavior change in emsdk 4.0.0] which breaks the load/init timing of the wasm module. FossilOrigin-Name: 00a750184bcf1a94bf4e7f1d5029a42671e87e2997ae97be07bd900d3702883d
* Ensure that the OPFS VFS's xOpen() writes back the read-only flag to the ↵stephan2024-10-17
| | | | | output flags. Resolves the problem reported in [forum:cf37d5ff1182c31081 | forum post cf37d5ff1182c31081]. FossilOrigin-Name: 0a32624015f16fd881a4ecbb56b7833391028d327a95f4c899eee864ed7fe00d
* When calling OpfsSAHPoolUtil.removeVfs(), ensure that the cached result the ↵stephan2024-10-17
| | | | | VFS init is also removed so that the VFS may later be registered again with the same name. Set up test code for the regression reported in [forum:cf37d5ff11 | forum post cf37d5ff11] (which uncovered the removeVfs() shortcoming) but that test is currently only known to fail with the "opfs" VFS and is not currently set up to fail. FossilOrigin-Name: b7f7a5deeae61920dbfec7606cf9014de711f959a285b29e12673abfd2f88646
* Remove a few more traces of long double from the code.drh2024-10-02
| | | FossilOrigin-Name: 11d6a89e4a25c3f884ff617036d239dc42522859400cd1f4674634f6c7adbb02
* Another comment about the LONGDOUBLE wasm topic. No code changes.stephan2024-10-01
| | | FossilOrigin-Name: 1755831cb1ac58241e0b11d8d003b5eca39b65aa3cb84229b215662028b1b3c0
* Use the new SQLITE_USE_LONG_DOUBLE to disable long-double support in WASM ↵stephan2024-10-01
| | | | | builds, as they cannot be represented in JS and this saves approximately 5.5kb in the resulting wasm file. FossilOrigin-Name: fa7b56f776b715d061581fad6f04b871504ff5d808e7364419d1d6cdef82c5ee
* Add an #if'd-out block to sqlite3-wasm.c mentioning the LONGDOUBLE_TYPE, as ↵stephan2024-10-01
| | | | | brought up in [forum:cbfb0d0ac0a4e349 | forum post cbfb0d0ac]. No functional changes. FossilOrigin-Name: 0b83e8f1ef53b35a9dda0740b4922b8691428f7484f3058833a961f3f8d0b178
* Wasm build cleanups. Fix the wasm speedtest1 builds broken by yesterday's ↵stephan2024-09-24
| | | | | refactoring. FossilOrigin-Name: 5d4a090230d1d7609e70b9c28d662dc8b0f8dd4d70a254f3ce6e449c68a25897
* Further wasm build cleanups and tweaks. No functional changes.stephan2024-09-24
| | | FossilOrigin-Name: 3b72a143431537ec275aefae739e56330c1d445c9ea80885882a2b9aa2201179
* Strip progress handlers and window functions from the wasm bare-bones ↵stephan2024-07-25
| | | | | (formerly 'minimal') JS bits, noting that we can't yet use OMIT_WINDOWFUNC (for the C parts) without a custom amalgamation. Currently at 604kb. FossilOrigin-Name: ec02e9237e1ef81c4196fa630822cb109eab926143ad09593a24273eb0668601
* More work on the minimal-mode wasm build (now 603kb uncompressed). Remove ↵stephan2024-07-25
| | | | | the hard-coded feature-enable flags from sqlite3-wasm.c and rely on the build to provide them. Some wasm build cleanup, but attempts to completely overhaul it have been thwarted by my inability to make script-generated makefile code more legible/maintainable than the current eval spaghetti. FossilOrigin-Name: b029c4067943e366a9b25b8303136fab10822bd771ea4658ac4cd716ff4a0d8f
* Start work on an overhaul of the wasm build process, with an eye towards ↵stephan2024-07-25
| | | | | less over-engineering. FossilOrigin-Name: ed746b3dd3248b68cb91de50ac5ba5fd3a7c2fcbde76324e86b88edbfecd896b
* wasm minimal build: strip authorizers and JSON support (saves approx 35kb). ↵stephan2024-07-24
| | | | | Strip vtab support from the JS bits but cannot yet strip it from the C bits because that requires a custom-configured sqlite3.c. FossilOrigin-Name: eb64d106551718467e0f6c6b53695410bf4c566901008e4cda8580d0f7efa7b0
* Restructuring of the wasm build to support an experimental 'minimal' build ↵stephan2024-07-24
| | | | | mode which elides all non-core APIs. FossilOrigin-Name: ee2191f7302210100fa0b29ace8156531ad995bf61aa2642e526e0901d0c6862
* Doc typo fix. No code changes.stephan2024-07-22
| | | FossilOrigin-Name: 8d558ad25bfbdea04de87616d4e3f664b5749a7d23643d1a0238e991b4bb337e
* Move a block of JS code which was inadvertently (and harmlessly) moved in ↵stephan2024-07-22
| | | | | the previous checkin. Clarify the semantics of an internal-use-only API. Add another WAL-related JS test. FossilOrigin-Name: 6cd9f55a975b5237efee8776efce7e7836b41905ca750f82be3b90aa04c1dff2
* OPFS VFSes: remove the on-open() pragma calls, as those (A) already ↵stephan2024-07-22
| | | | | reflected the build-time default settings and (B) they made it illegal to run locking_mode=exclusive, which is a requirement for WAL mode without shared memory. Modify part of the test suite to demonstrate that the SAHPool VFS can run in WAL mode so long as locking_mode=exclusive is used. FossilOrigin-Name: 19cd8e2b056d7842ee39afb7160c901c9dc55a5bac8049cb0b5246210f6b920d
* Slight doc touchup for [af41a1e6fc8b36e9bf65] based on feedback. No code ↵stephan2024-07-15
| | | | | changes. FossilOrigin-Name: be7b1fc0c5d8cda971b471dfcb4637212bfff4f42b1e074077a381cc493d877a
* Add JS binding for sqlite3_column_decltype().stephan2024-07-13
| | | FossilOrigin-Name: 5252d292b14f6ed99b09f6330b19effd488c2b23ff6ea33311321a065d3f6ce2
* JS doc touchups. No code changes.stephan2024-07-13
| | | FossilOrigin-Name: a8e240495ff7e0cd38301ef2de215a7cc10fea832311bd19ca2592858ee4e6ff
* Add JS bindings for sqlite3_stmt_busy() and sqlite3_stmt_explain().stephan2024-07-13
| | | FossilOrigin-Name: b772edfb44143107d4993bde600d0f4c45184f29a4deee403105c64748c36523
* Add missing sqlite3_bind_parameter_name() binding to JS.stephan2024-07-13
| | | FossilOrigin-Name: 6dcfcc7e1c0772b11aec750bb75899a5c8e452735ecf5028c001fbaa7aa6fda0
* Add JS bindings and tests for sqlite3_interrupted(), is_interrupted(), and ↵stephan2024-07-13
| | | | | db_readonly(). FossilOrigin-Name: 5589ba5651d80479ae555429340fc74390ff07d3e05ba770bb7d82490211e00d
* Remove a stray/harmless duplicate wasm function export entry.stephan2024-07-13
| | | FossilOrigin-Name: 5402e4fb1cbd7a2c3dee6ebfb492a076d05daa66f747d18602338874405829df
* Add an option to the opfs-sahpool VFS which tells it to ignore a previous ↵stephan2024-07-13
|\ | | | | | | | | init failure and retry, as an opt-in workaround for a browser quirk which occasionally denies OPFS access on the first attempt and permits it on subsequent attempts. This resolves [https://github.com/sqlite/sqlite-wasm/issues/79|issue #79 of the npm distribution]. FossilOrigin-Name: fbf3948a4ba27c6ebf55b24e7463b20026439f04d1974bafe78df5c5bc958f59
| * Rename the new opfs-sahpool init-retry flag to the suitably descriptive, and ↵stephan2024-07-13
| | | | | | | | | | suitably onerous, forceReinitIfPreviouslyFailed, based on feedback. FossilOrigin-Name: c9f0a6090258534a3d81066df5610229183a8457fc60d5034b4b94d9a29796e4
generated by cgit v1.2.3 (git 2.25.1) at 2025-05-21 17:22:25 +0000