1. 23
  1.  

  2. 8

    The default built-in storage engine is a log-structured merge database. It is very fast, faster than LevelDB, supports nested transactions, and stores all content in a single disk file.

    Damn. Time to go read that source code.

    1. 3

      I hope you report back with your findings!

      1. 1

        Do you know if sqlite4 is ready for usage? Sqlite.org doesn’t have any direct reference to it, you seem to have to know about the src4 URL to get to it and then you have to pull the code directly from fossil as far as I can tell..

        1. 1

          It doesn’t seem to be generally available so I’m guessing no.

      2. 4

        Is there a reason this link is suddenly popular, other than the fact it’s suddenly popular?

        There doesn’t appear to have been any actual activity regarding development of sqlite4 in several years.

        1. 3

          I have no idea about your first question, but there’s been plenty of development; check out https://www.sqlite.org/src4/timeline. And no, I have no idea why that’s not stored in a branch in the main SQLite Fossil repo.

          1. 2

            Good to know. I couldn’t tell if that was fix merges from sqlite3 or not, so then I checked the wiki history, which is rather barren. https://www.sqlite.org/src4/timeline?n=20&y=w

            The web interface to fossil is…

            1. 1

              …at least extant, making it better than out-of-the-box Git?

              1. 1

                Hm? Gitweb is in mainline git (and apparently has been since version 1.4), and is included in a completely vanilla ./configure && make && make install installation…

                1. 1

                  Fossil’s web interface is a genuine GUI, permitting altering commits, browsing history, adding users, browsing the project wiki, tracking bugs, and so on. It’d be as if Git bundled GitLab, and versioned all of GitLab’s data in the Git repo itself. I’m not a huge Fossil fan—in fact, I don’t really follow it, and use it for no projects whatsoever myself—but it’s the only system I’ve encountered that tries to include the whole vertical hosting solution right in the base install. This is radically different from what you get via instaweb or hg serve, even if it is surprisingly unintuitive in practice.