Skip to content

Releases: proofrock/ws4sqlite

Version v0.16.2

19 Jun 13:39
9e1cf2a
Compare
Choose a tag to compare

📢 This project was forked to ws4sql, the "next" version that will support more databases than sqlite (hence the new name, if you noticed 😉). It will take some time, through improvements and, alas, breaking changes. The development will happen in the fork/ws4sql branch, and you can find the changes and the steps needed to migrate a regular installation in the ROAD_TO_WS4SQL.md document.

📢 I started a discussion over the future direction for this project. Take a look, and chip in if you want!

Aligned to SQLite 3.46.0. Compiled with go 1.22.4.

  • SQLite 3.46.0
  • Library updates

Docker images for amd64, arm and arm64 are here.

This release is backwards compatible with v0.11.x, and the existing client libraries don't need to be changed.

[fork] ws4sql v0.17dev2

05 May 13:16
Compare
Choose a tag to compare
Pre-release

This is a second pre-release of a new fork of ws4sqlite, that will "transit" the app to a new version that will support more databases than sqlite (hence the new name, if you noticed 😉). It will take some time, through improvements and, alas, breaking changes.

This is not the latest release of ws4sqlite, which is still here.

The work will take place in the fork/ws4sql branch, and you can find the changes so far, and the steps needed to migrate a regular installation in the ROAD_TO_WS4SQL.md document.

Docker images for amd64 and aarch (arm64) are at docker pull germanorizzo/ws4sql:latest

In this release

  • [BREAKING] When running the app, the config files must be specified on the command line, the file paths cannot be used anymore (there). This is described in the "Migration" section below. The file path is in the config file.
  • The only exception is a "simple case" to serve a file path without any config. This can be done with the new --quick-db parameter.

Migration

  • For any --db and --mem-db switch that was used, an explicit YAML config file must be created. The format is the same, but there is a new section at the beginning:
database:
  type: SQLITE          # Only SQLITE for now. If omitted, defaults to SQLITE      
  inMemory: false       # If type = SQLITE. The db is a memory one? If omitted, defaults to false
  path: ".../test.db"   # If type = SQLITE. The db file path.
  id: test              # If omitted and !inMemory, calculates it from the file name (if type = SQLITE)
  disableWALMode: false # If type = SQLITE. Same as before, but moved here.
  readOnly: false       # Same as before, but moved here.

As always, your feedback is deeply appreciated, if you'll be so kind. Cheers! 🍻

[fork] ws4sql v0.17.0beta1

28 Apr 15:55
Compare
Choose a tag to compare
Pre-release

This is a first pre-release of a new fork of ws4sqlite, that will "transit" the app to a new version that will support more databases than sqlite (hence the new name, if you noticed 😉). It will take some time, through improvements and, alas, breaking changes.

This is not the latest release of ws4sqlite, which is still here.

The work will take place in the fork/ws4sql branch, and you can find the changes so far, and the steps needed to migrate a regular installation in the ROAD_TO_WS4SQL.md document.

In this release:

  • Renamings
  • SQLite is now provided by mattn/go-sqlite3 and CGO. Should be quite faster.
    • CGO will be needed by other, future features, so it's a good point to reintroduce it
  • Target platforms (because of CGO) are now 6 (win/amd64, macos/amd64, macos/arm64, linux/amd64, linux/arm64, linux/arm6)

As always, your feedback is deeply appreciated, if you'll be so kind. Cheers! 🍻

Version v0.16.1

18 Apr 06:27
Compare
Choose a tag to compare

📢 I started a discussion over the future direction for this project. Take a look, and chip in if you want!

Aligned to SQLite 3.45.2. Compiled with go 1.22.0.

  • SQLite 3.45.1
  • Library updates (incl. security fixes upstream)

Docker images for amd64, arm and arm64 are here.

This release is backwards compatible with v0.11.x, and the existing client libraries don't need to be changed.

Version v0.16.0

17 Feb 15:51
Compare
Choose a tag to compare

📢 I recently started a discussion over the future direction for this project. Take a look, and chip in if you want!

Aligned to SQLite 3.45.1. Compiled with go 1.22.0.

  • #38: In a map resultset, keys are now in the same order as in the query
  • #41: Query parameters as arrays
  • #42: Remove encryption framework (breaking change)
  • #43: Option to return results as a list, instead of a map
  • Go 1.22 and SQLite 3.45.1

Docker images for amd64, arm and arm64 are here.

This release is backwards compatible with v0.11.x, and the existing client libraries don't need to be changed.

Version v0.15.3

09 Feb 20:00
Compare
Choose a tag to compare

This project has now a reimplementarion in Rust, called sqliterg, at sqliterg.dev. It is not a 1:1 rewrite, but I tried to fix some concepts that I feel I got wrong here; plus it's smaller, (even) faster, (even) less memory-hungry and it can be built with an embedded sqlite or using the one on the system. You should feel at home with it, anyway a migration guide is here.

ws4sqlite is not really deprecated, it will continue to receive libraries updates (about monthly), but probably not new features.

Aligned to SQLite 3.41.2. Compiled with go 1.21.6.

  • CI with Github Actions
  • Switched to trunk based workflow
  • Library updates (incl. security fixes upstream)

Docker images for amd64, arm and arm64 are here.

This release is backwards compatible with v0.11.x, and the existing client libraries don't need to be changed.

v0.15.2

03 Dec 20:33
Compare
Choose a tag to compare

This project has now a reimplementarion in Rust, called sqliterg, at sqliterg.dev. It is not a 1:1 rewrite, but I tried to fix some concepts that I feel I got wrong here; plus it's smaller, (even) faster, (even) less memory-hungry and it can be built with an embedded sqlite or using the one on the system. You should feel at home with it, anyway a migration guide is here.

ws4sqlite is not really deprecated, it will continue to receive libraries updates (about monthly), but probably not new features.

Aligned to SQLite 3.41.2. Compiled with go 1.21.4.

  • Library updates (incl. security fixes upstream)

Docker images for amd64, arm and arm64 are here.

This release is backwards compatible with v0.11.x, and the existing client libraries don't need to be changed.

v0.15.1

06 Oct 14:41
Compare
Choose a tag to compare

This project has now a reimplementarion in Rust, called sqliterg, at sqliterg.dev. It is not a 1:1 rewrite, but I tried to fix some concepts that I feel I got wrong here; plus it's smaller, (even) faster, (even) less memory-hungry and it can be built with an embedded sqlite or using the one on the system. You should feel at home with it, anyway a migration guide is here.

ws4sqlite is not really deprecated, it will continue to receive libraries updates (about monthly), but probably not new features.

Aligned to SQLite 3.41.2. Compiled with go 1.21.2.

  • Library updates

Docker images for amd64, arm and arm64 are here.

This release is backwards compatible with v0.11.x, and the existing client libraries don't need to be changed.

v0.15.0

07 May 13:30
Compare
Choose a tag to compare

Aligned to SQLite 3.41.2. Compiled with go 1.20.4.

  • Issue #29: Allow different path for db companion YAML file
  • Issue #28: Rework build system
  • Issue #27: Add support for linux/S390x
  • Documentation regarding #33 (Dockerfile: allow specifying UID/GID with which ws4sqlite starts)
  • Library updates

Docker images for amd64, arm and arm64 are here.

This release is backwards compatible with v0.11.x, and the existing client libraries don't need to be changed.

v0.14.2

21 Apr 09:52
Compare
Choose a tag to compare

Aligned to SQLite 3.41.2. Compiled with go 1.20.3.

  • Issue #25: Rebase docker image(s) on distroless/static-debian11
  • Issue #26: When checking file/dir existence, manage all errors
  • Some minor improvements to build
  • Library updates

Docker images for amd64, arm and arm64 are here.

This release is backwards compatible with v0.11.x, and the existing client libraries don't need to be changed.