[fork] ws4sql v0.17dev3
Pre-releaseThis is a third 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.
Compiled in Github Actions using Go 1.23.4. Docker images for amd64 and aarch64 (arm64) are at docker pull ghcr.io/proofrock/ws4sql:latest
.
In this release
- DuckDB initial support added. It should work, as all the tests pass; it's not tested extensively in real life, of course. Limitations are listed in
ROAD_TO_WS4SQL.md
, under the sectionSpecific to DuckDB
. - Docker images are now based on
debian/12-slim
(see #49). - Docker images are now hosted on Github's Container Registry.
- Libraries updates.
NB: binaries for linux/arm64
are compiled under Raspbian, not static. Please let me know of any issue; I have a problem with CI that doesn't allow static compilation.
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 # SQLITE or DUCKDB. If omitted, defaults to SQLITE
inMemory: false # If type = SQLITE|DUCKDB. The db is a memory one? If omitted, defaults to false
path: ".../test.db" # If type = SQLITE|DUCKDB. The db file path.
id: test # If omitted and !inMemory, calculates it from the file name (if type = SQLITE|DUCKDB)
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! 🍻