Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
15 events for the month beginning 2024-04-01 by user stephan
Following month ↑|
2024-04-26
| ||
| 18:42 | Internal JS doc touchups. No functional changes. (check-in: 626b997b user: stephan tags: trunk) | |
| 18:24 | Additional internal docs in the wasm utilities. (check-in: 5a2245a9 user: stephan tags: trunk) | |
|
2024-04-25
| ||
| 06:52 | wasm: add a makefile comment about the static sqlite3.h/c version info injected into the JS files possibly differing from the runtime-emited version info when a user provides their own sqlite3.c. (check-in: d99a01a0 user: stephan tags: trunk) | |
|
2024-04-24
| ||
| 06:43 | Remove an undocumented feature from the JS Worker1.open API because it relies on broken behavior which has no VFS-agnostic workaround. (check-in: 3a640038 user: stephan tags: trunk) | |
|
2024-04-23
| ||
| 06:49 | Remove some dead WASM-side code. (check-in: 0a07ee27 user: stephan tags: trunk) | |
| 06:36 | Minor touchups in JS docs and exception messages. (check-in: 9e7fc937 user: stephan tags: trunk) | |
| 05:38 | When running the 'dist' target in ext/wasm for an SEE-capable build, ensure that the resulting zip file and directory name include '-see'. (check-in: 04c552b1 user: stephan tags: trunk) | |
|
2024-04-22
| ||
| 17:03 | Minor cleanups to [8fbda563d2f5]. (check-in: 5ee2594b user: stephan tags: trunk) | |
| 16:46 | Extend the JS/WASM SEE build support by (A) filtering SEE-related bits out of the JS when not building with SEE and (B) accepting an optional key/textkey/hexkey option to the sqlite3.oo1.DB and subclass constructors to create/open SEE-encrypted databases with. Demonstrate SEE in the test app using the kvvfs. This obviates the changes made in [5c505ee8a7]. (check-in: 8fbda563 user: stephan tags: trunk) | |
| 11:48 | For sqlite3.oo1.DB JavaScript classes, bypass execution of any on-open() SQL in SEE-capable builds because it would necessarily run before the client has an opportunity to provide their decryption key, which would leave the db handle in an unusable state and cause the ctor to throw. This currently affects only the OPFS VFSes. We may want to consider extending the ctor options object to optionally accept an SEE key and apply it when opening the db. (check-in: 5c505ee8 user: stephan tags: trunk) | |
|
2024-04-11
| ||
| 19:09 | Fix handling of the SQLITE_OMIT_WAL check in one place. Resolves forum post 87cc13302de160eb. (check-in: ce86d30d user: stephan tags: branch-3.45) | |
| 19:08 | Fix handling of the SQLITE_OMIT_WAL check in one place. Resolves forum post 87cc13302de160eb. (check-in: 5dae6e6d user: stephan tags: trunk) | |
|
2024-04-04
| ||
| 22:53 | Optimize sqlite3.oo1.DB.exec() for the rowMode='object' case to avoid converting the object property keys (column names) from native code to JS for each row. This speeds up large data sets considerably and addresses the report in forum post 3632183d2470617d. (check-in: 8b41ef86 user: stephan tags: trunk) | |
| 12:37 | Fix exception propagation when the opfs-sahpool VFS fails to initialize to address report in forum post be0141c639. (check-in: db31d178 user: stephan tags: branch-3.45) | |
| 12:36 | Fix exception propagation when the opfs-sahpool VFS fails to initialize to address report in forum post be0141c639. (check-in: cdb3a900 user: stephan tags: trunk) | |