sqlite3 fiddle
With all my SQL and SQLite posts, this link is probably also quite interesting: sqlite3 fiddle.
With all my SQL and SQLite posts, this link is probably also quite interesting: sqlite3 fiddle.
I am convinced of SQLite. For many use cases where other databases like MySQL, MariaDB or PostgreSQL are often used, SQLite would suffice, given the right design and architecture.
On Saturday morning I experimented a bit. Whenever I used SQLite in a Go application, I used the popular package mattn/go-sqlite3. Not a bad choice, after all it implements the database/sql interface. One drawback, however, is the need for a C compiler, since Cgo is used to run the original SQLite code in the background.
I like listening to interviews with SQLite developer Richard Hipp (as you may know). He’s a great storyteller and you can always learn something new from him. This podcast episode is no exception.
I configured Litestream for all my GoBlog-instances. This means that the changes to the SQLite databases, are replicated directly into an object storage at Scaleway. Why? An additional backup never hurts.
I found two SQLite related articles in my Pocket list, which I wanted to share.
I am a fan of SQLite. SQLite is brilliant, offers a lot of features, but is often underestimated. Also my blog uses SQLite, as well as my URL shortener.
Martin Tournoij wrote about “stupid light software”. When you try to be a bit too minimalistic with your software, it’s probably “stupid light software”.
Yesterday, I watched this interview from Federico Razzoli with the creator of SQLite Richard Hipp. I learned some more background facts about SQLite or understood things I wasn’t so sure about before.
Productive Sunday morning: I just integrated a full-text search into GoBlog. It’s using the SQLite FTS5 extension. I always find it impressive how many features SQLite has and what is possible with it!
Feel free to try the new search (on the English blog - or on the German one). 🤓