SQLite version 3.39.0 beta
(1) By Richard Hipp (drh) on 2022-05-26 12:45:51 [source]
We hope to release SQLite version 3.39.0 before too long. Please take a moment to review the change log and try it out. Do your best to break this beta and report any problems you find either on this forum, or directly to me at drh at sqlite dot org.
Source code for a recent 3.39.0 beta can be found as the "Pre-Release Snapshot" on the Download Page
Run The Latest SQLite 3.39.0 Beta Directly In Your Web Browser
If you prefer, you can experiment with the latest 3.39.0 code directly in your web-browser and without having to download or install anything by visiting https://sqlite.org/fiddle/. (The page name is by analogy to sites like "JSFiddle" and "SQLFiddle".) The https://sqlite.org/fiddle/ page runs a WASM-compiled copy of a recent 3.39.0 build in a sandbox in your web browser. Using controls on that page, you can import database files from your local machine (assuming they aren't too big), work with them, then export any changes back to your desktop.
(2) By anonymous on 2022-05-26 14:41:58 in reply to 1 [link] [source]
Documentation issue: are sqlite3_db_name database numbers 0-based or 1-based?
(3) By anonymous on 2022-05-26 14:57:06 in reply to 2 [link] [source]
Also "An N alue" should be "An N value".
(4) By anonymous on 2022-05-26 16:29:49 in reply to 3 [link] [source]
It would be very handy to be able to highlight an expression and click RUN to have that highlighted expression executed.
(5) By Stephan Beal (stephan) on 2022-05-26 16:36:19 in reply to 4 [link] [source]
It would be very handy to be able to highlight an expression and click RUN to have that highlighted expression executed.
That's a nice idea. Added to the TODO list. The JS selection-related APIs are somewhat awkward, but this will otherwise be easy to add.
(6) By Stephan Beal (stephan) on 2022-05-27 03:29:34 in reply to 4 [link] [source]
It would be very handy to be able to highlight an expression and click RUN to have that highlighted expression executed.
That is now implemented (not yet deployed) but has one minor caveat: clicking the RUN button unhighlights the selected text (on my platform, at least), but it's still selected, so the button behaves properly but may give a slightly confusing impression because the part it's running is not clearly highlighted. That may well be a browser-specific quirk.
Tapping ctrl-/shift-enter will also now submit only the selected text.
(7.1) By Simon Slavin (slavin) on 2022-05-27 13:55:45 edited from 7.0 in reply to 1 [link] [source]
The unix os interface resolves all symbolic links in database filenames to create a canonical name for the database before the file is opened.Does this mean that journal files will now be created in the directory of the database rather than the directory of the link ?
Does this mean that SQLite on Unix now behaves the same as SQLite on Windows (with regard to this) ?
Should section 2.5 of https://www.sqlite.org/howtocorrupt.html be updated ?
Please excuse me for the interrogation, but this fixes something I got bitten by in a sandbox implementation a few years ago.
(8) By Richard Hipp (drh) on 2022-05-27 14:09:39 in reply to 7.0 [link] [source]
Does this modify section 2.5 of https://www.sqlite.org/howtocorrupt.html ?
Hard links and symbolic links are not the same thing. The enhancement resolves symbolic links. Section 2.5 talks about hard links.
(9) By Kevin Charles (KevinCharles) on 2022-05-27 23:28:02 in reply to 1 [link] [source]
Thanks, very useful.
My DB I experimented with is 1/3 of a Gigabyte, no problems.
Normally I use Sqlitebrowser or Linux terminal.
Handy using sqlite within Firefox within Ubuntu Linux.
I've got a new Android phone, normal size screen, gave it a go, text is tiny, with plenty of blank space. Expands OK.
I'll give it a go in Windows a bit later.