Skip to content

Releases

Version 3.0.0

Choose a tag to compare

@StormBytePP StormBytePP released this 04 Nov 13:08

[Summary]

StormByte Database is the C++26 SQL layer of the StormByte suite.

One API covers SQLite, PostgreSQL, MariaDB and Microsoft SQL Server (MSSQL).
Backends are base classes: you derive your schema, prepare statements and hook connect there.
This repository is not Base, Buffer, Config, Crypto, Logger, Multimedia, Network or System.
It requires StormByte Base 3.0.0 and StormByte-Logger 3.0.0.
The original StormByte-Database source is dual-licensed under LGPL v3.0-or-later or a commercial license.

If you landed here from a release link and have not read the tree:

Added

  • Install FindStormByteDatabase.cmake so Base 3.0.0 can discover Database as a component. Verify consumers against both an installed prefix and an extracted release ZIP.

Changed

  • Breaking: Require Base 3.0.0 component discovery and use the Linux archive naming scheme with architecture, libc and C++ standard library.
  • Require StormByte-Logger 3.0.0 and StormByte-BuildMaster 2.1.5.
  • Stop forcing CPU and optimization flags in manual Release builds; CPU selection now comes from the toolchain while ENABLE_LTO remains independently configurable.

Fixed

  • PGO training runner now prepends its library directories to LD_LIBRARY_PATH/DYLD_LIBRARY_PATH with the : separator (previously ;, which broke library lookup on musl) and no longer appends an empty entry when the variable is unset.
  • Reconfigure automatically when VERSION changes so rebuilt and installed artifacts use the updated project version.
  • Restore OFF, SYSTEM and BUNDLED backend coverage for every Linux CI architecture, libc and C++ runtime combination, with system development packages installed inside Alpine for musl builds.
  • Keep macOS and Windows CI to one BUNDLED variant each.
  • Run SQL Server integration within the Linux amd64 backend matrix and skip it on ARM64 when no server is configured.
  • Build GNU gperf 3.3 from its verified official source archive with a CMake port when FreeTDS cannot use a system gperf, fixing the bundled build with GCC 15 on musl.
  • Enable C++ exception handling for the bundled gperf tool with MSVC-compatible compilers, fixing the Windows clang-cl build.
  • Correct bundled FreeTDS linking with strict linkers.

Version 2.1.3

Choose a tag to compare

@StormBytePP StormBytePP released this 02 Nov 08:02

[Summary]

StormByte Database is the C++26 SQL layer of the StormByte suite.

One API covers SQLite, PostgreSQL, MariaDB and Microsoft SQL Server (MSSQL).
Backends are base classes: you derive your schema, prepare statements and hook connect there.
This repository is not Base, Buffer, Config, Crypto, Logger, Multimedia, Network or System.
It requires StormByte Base 2.2.3 and StormByte-Logger 2.0.6.
The original StormByte-Database source is dual-licensed under LGPL v3.0-or-later or a commercial license.

If you landed here from a release link and have not read the tree:

Fixed

  • Windows CI and release builds retry transient Chocolatey failures when installing NASM and jom, and require each executable to be available before accepting installation as successful.

Changed

  • Bundled builds use Base 2.2.3 and Logger 2.0.6.
  • Rebuild release packages against the refreshed Base 2.2.3 and Logger 2.0.6 releases, including their final audit fixes.
  • Bundled OpenSSL builds disable SSLv3 and TLS compression while retaining modern TLS versions and the existing cipher algorithm set.

Version 2.1.2

Choose a tag to compare

@StormBytePP StormBytePP released this 28 Oct 02:28

[Summary]

StormByte Database is the C++26 SQL layer of the StormByte suite.

One API covers SQLite, PostgreSQL, MariaDB and Microsoft SQL Server (MSSQL).
Backends are base classes: you derive your schema, prepare statements and hook connect there.
This repository is not Base, Buffer, Config, Crypto, Logger, Multimedia, Network or System.
It requires StormByte Base 2.2.2 and StormByte-Logger 2.0.5.
The original StormByte-Database source is dual-licensed under LGPL v3.0-or-later or a commercial license.

If you landed here from a release link and have not read the tree:

Changed

  • Bundled builds use Base 2.2.2 and Logger 2.0.5. Require BuildMaster 2.1.3 and pin its bundled submodule to the published release.

Version 2.1.1

Choose a tag to compare

@StormBytePP StormBytePP released this 24 Oct 19:23

[Summary]

StormByte Database is the C++26 SQL layer of the StormByte suite.

One API covers SQLite, PostgreSQL, MariaDB and Microsoft SQL Server (MSSQL).
Backends are base classes: you derive your schema, prepare statements and hook connect there.
This repository is not Base, Buffer, Config, Crypto, Logger, Multimedia, Network or System.
It requires StormByte Base 2.2.1 and StormByte-Logger 2.0.4.
The original StormByte-Database source is dual-licensed under LGPL v3.0-or-later or a commercial license.

If you landed here from a release link and have not read the tree:

Changed

  • Bundled third-party StormByte dependencies now require the matching patch releases (Base 2.2.1, Buffer 2.0.4, Logger 2.0.4, System 2.1.1 where applicable) so a bundled build picks up the /arch:AVX change.

Changed

  • Windows Release optimizations use /arch:AVX instead of /arch:AVX2. The previous baseline required a Haswell-or-newer CPU (AVX2). /arch:AVX runs on Sandy Bridge and Ivy Bridge (including the i7-3770K) and later.

Version 2.1.0

Choose a tag to compare

@StormBytePP StormBytePP released this 23 Oct 15:59

[Summary]

StormByte Database is the C++26 SQL layer of the StormByte suite.

One API covers SQLite, PostgreSQL, MariaDB and Microsoft SQL Server (MSSQL).
Backends are base classes: you derive your schema, prepare statements and hook connect there.
This repository is not Base, Buffer, Config, Crypto, Logger, Multimedia, Network or System.
It requires StormByte Base 2.2.0 and StormByte-Logger 2.0.3.
The original StormByte-Database source is dual-licensed under LGPL v3.0-or-later or a commercial license.

If you landed here from a release link and have not read the tree:

Added

  • Generated and installed StormByte/database/backend.hxx with enum class Backend and constexpr Available(Backend) noexcept. Applications can determine which backends were compiled into the library before opening a connection: SYSTEM and BUNDLED return true, while OFF and unknown enum values return false. Backend tests check availability at compile time, and the API is included in the Doxygen reference.

Changed

  • Split thirdparty/StormByte into base and logger subcomponents, following Buffer's layout, and updated their release archives to StormByte Base 2.2.0 and StormByte-Logger 2.0.3. SYSTEM/BUNDLED selection and static/shared linking are unchanged.

Fixed

  • CI and release initialize MariaDB as the mysql service user rather than asking the bootstrap server to switch UID/GID. Bootstrap uses --no-defaults and explicit command-line settings instead of a configuration file in /tmp that the server could not open. This addresses the initialization failures observed after ubuntu-latest moved to Ubuntu 26.04, while preserving root administration through Unix-socket authentication.

Version 2.0.2

Choose a tag to compare

@StormBytePP StormBytePP released this 19 Oct 21:03

[Summary]

StormByte Database is the C++26 SQL layer of the StormByte suite.

One API covers SQLite, PostgreSQL, MariaDB and Microsoft SQL Server (MSSQL).
Backends are base classes: you derive your schema, prepare statements and hook connect there.
This repository is not Base, Buffer, Config, Crypto, Logger, Multimedia, Network or System.
It requires StormByte Base 2.1.0 and StormByte-Logger 2.0.2.
The original StormByte-Database source is dual-licensed under LGPL v3.0-or-later or a commercial license.

If you landed here from a release link and have not read the tree:

Added

  • Release workflow. The archive name is StormByte-Database-<tag>-<os>-<arch>[-stdlib].zip. The build compiles SQLite, PostgreSQL, MariaDB and the MSSQL client, and starts PostgreSQL and MariaDB before the build so PGO training can run those tests. On Linux the MSSQL container is started as well. macOS and Windows have no SQL Server during a tag build, so that test skips.
  • THIRD-PARTY (hyphenated: THIRDPARTY is the same path as the thirdparty/ directory on Windows and macOS) plus COPYING.SQLite, COPYING.PostgreSQL, COPYING.MariaDB, COPYING.FreeTDS and COPYING.OpenSSL. The MSSQL objects are FreeTDS DB-Library, tds, replacements and tdsutils only, under the GNU Library General Public License v2 or later. The FreeTDS server, ODBC driver, CT-Library and tools are not compiled in. OpenSSL 3.5.9 is compiled in because those clients link it.
  • ENABLE_LTO and ENABLE_PGO. CI keeps the compiler and dependency matrix, turns LTO on and runs the tests. Profile-guided optimization, and the documentation, stay on the release workflow.

Fixed

  • InstalledConsumerSmoke also searches the directory of a system StormByte-Logger. WITH_STORMBYTE=SYSTEM does not copy that library into the BuildMaster prefix, so the smoke test failed configure with Could not find LOGGER_LIBRARY and aborted PGO.
  • -stdlib=libc++ and -stdlib=libstdc++ do not count as custom C++ flags. If either is the only extra flag, Release still gets -O2 and the CPU baseline.
  • Bundled MariaDB Connector C no longer builds mariadb_config. WITH_UNIT_TESTS=OFF already skips the connector test suite, and WITH_TOOLS is off, but the helper executable is unconditional on Unix. Its main shares a name with the test programs in the merged Clang profile, so -fprofile-use reports a control-flow hash mismatch and the connector's -Werror aborts the build. The library does not use that executable.
  • MSVC PGO no longer puts /LTCG:PGINSTRUMENT or /LTCG:PGOPTIMIZE in CMAKE_EXE_LINKER_FLAGS. Those flags are add_link_options on this project. A nested project() inherits the cache and its compiler test links cmTC_*.exe, which was never instrumented, so /LTCG:PGOPTIMIZE aborted with LNK1266 (cmTC_*.pgd missing). The cache keeps a bare /LTCG so those /GL objects still link. A static dependency stays LTCG and is optimized by the link that owns the .pgd.
  • Bundled PostgreSQL on Windows is built without LTO. MSVC LTCG left postgres.lib without the backend exports, so libpqwalreceiver.dll failed to link (ResetLatch, ProcessInterrupts and the rest). The client archives are still static.
  • Clang PGO drops .profraw files left by compiler probes before ctest, and llvm-profdata merge uses -failure-mode=all. A probe writes a few hundred bytes for main, with a padded empty symbol name. The default failure mode is any, so that one file aborted the merge even after the instrumented tests had passed.
  • Postgres sends port to PQconnectdbParams. The connection used to omit it, so libpq used 5432 or PGPORT instead of the port this object was given. The constructor takes the port after the logger and defaults to 5432. Callers that do not pass it stay source-compatible.

Changed

  • CI builds with ENABLE_LTO=ON, ENABLE_PGO=OFF and ENABLE_TEST=ON, then runs ctest. Profile-guided optimization stays on the release workflow.
  • Breaking: Database exceptions no longer call std::format. Literal {} is replaced by Safe::String::ReplaceToken, the same way Base, Config and Logger do it. what() paths are unchanged (StormByte.Database.Connection, StormByte.Database.Query.Execute, and the rest). Copy, move and each destructor stay in this module.
  • StormByte Base 2.1.0 and StormByte-Logger 2.0.2 are downloaded release archives (BACKEND=binary). The Logger source tree is no longer a submodule. BuildMaster 2.1.0 is required. optimizations.cmake matches the other modules: Linux x86-64-v3, Apple apple-m1, Windows /O2 /arch:AVX2. No /fp:fast.
  • Postgres and MariaDB tests read the account from the environment. POSTGRES_USER, POSTGRES_PASSWORD and POSTGRES_PORT default to testuser, testpass and 5432. MARIADB_USER, MARIADB_PASSWORD and MARIADB_PORT default to testuser, testpass and 3306. The host and the database name stay localhost or 127.0.0.1, and stormbyte_test.

Version 2.0.1

Choose a tag to compare

@StormBytePP StormBytePP released this 13 Oct 05:25

[Summary]

StormByte Database is the C++26 SQL layer of the StormByte suite.

One API covers SQLite, PostgreSQL, MariaDB and Microsoft SQL Server (MSSQL).
Backends are base classes: you derive your schema, prepare statements and hook connect there.
This repository is not Base, Buffer, Config, Crypto, Logger, Multimedia, Network or System.
It requires StormByte-Logger 2.0.0 or newer, which supplies the bundled text and StormByte Base dependencies.
The original StormByte-Database source is dual-licensed under LGPL v3.0-or-later or a commercial license.

If you landed here from a release link and have not read the tree:

Changed

  • Updated dependency pins.
  • Bumped the project version to 2.0.1.

Version 2.0.0

Choose a tag to compare

@StormBytePP StormBytePP released this 10 Oct 14:29

[Summary]

StormByte Database is the C++26 SQL layer of the StormByte suite.

One API covers SQLite, PostgreSQL, MariaDB and Microsoft SQL Server (MSSQL).
Backends are base classes: you derive your schema, prepare statements and hook connect there.
This repository is not Base, Buffer, Config, Crypto, Logger, Multimedia, Network or System.
It requires StormByte-Logger 2.0.0 or newer, which supplies the bundled text and StormByte Base dependencies.
The original StormByte-Database source is dual-licensed under LGPL v3.0-or-later or a commercial license.

If you landed here from a release link and have not read the tree:

Changed

  • DLL boundary — Hardened provider-owned storage while preserving inheritable database facades:
    • Hid the prepared-statement registry behind an opaque Safe::Unique owner on Base's heap and migrated its entries to Safe::Map<Safe::String, Safe::Shared<Safe::Unique<PreparedSTMT>>>. Creator-module callbacks retain map nodes and allocator state; copyable handles keep each statement uniquely owned without changing inheritable factories returning Safe::Unique.
    • Column names and prepared-statement names and SQL text use Safe::String, so inline accessors no longer interpret another module's standard strings.
    • Migrated private connection settings in inheritable PostgreSQL, MariaDB and MSSQL backends, PostgreSQL's server-side statement name and MSSQL's callback diagnostics to Base-owned Safe::String. Rows and positional prepared values use Base-owned Safe::Vector/Safe::Map; telemetry counters use Safe::Atomic. Native connection and statement handles are hidden behind semantic holders defined in non-installed private headers, while client-specific temporary buffers remain local to Database implementations. Safe allocation ownership does not remove the compatible C++ ABI, RTTI, calling-convention and provider-lifetime requirements for derived objects.
    • SQLite's protected native-path constructors convert to Base-owned UTF-8 in forced-inline caller adapters; rvalue paths no longer transfer caller STL allocations to the Database DLL, and Windows paths use SQLite's UTF-8 encoding.
    • Exported values, rows, transactions, database facades, prepared statements and telemetry declare STORMBYTE_DECLARE_MAYBE_SAFE with compatible-ABI and provider-lifetime requirements. Consumer derivatives remain responsible for their additional state and their own conditional declaration.
  • MSSQL backend — Added an optional Microsoft SQL Server backend using the LGPL FreeTDS DB-Library client. Bundled builds compile only the static DB-Library and its required TDS support archives; logical prepared statements use sp_executesql RPC with typed, separately transmitted parameters.
  • StormByte Suite port — Migrated first-party repository and documentation links to StormByte-Suite, removed the retired String repository from the suite listing and Doxygen tag references, and updated the Logger and BuildMaster submodule URLs.
  • Database API and connection behavior
    • Breaking: Removed accessor Get/Set prefixes: GetTelemetry() becomes Telemetry(), protected SetTelemetry(handle) becomes Telemetry(handle), and GetSslMode() / SetSslMode(mode) become SslMode() / SslMode(mode). Value::Get<T>() is unchanged. Backend text-member layouts changed with the Safe storage migration; rebuild derived consumers.
    • Breaking: BeginTransaction now returns Expected<Transaction, TransactionError> instead of throwing when transaction start fails. Database construction may also report allocation failure rather than terminating from a noexcept constructor; rebuild consumers against this API revision.
    • Breaking: The public API contract changed beyond the DLL boundary fix. Inputs and storage use StormByte 2.0 types (StormByte::Safe::String, StormByte::Safe::Binary, StormByte::Size, StormByte::ByteSize, std::string_view), backend logger ownership is StormByte::Safe::Shared<Logger::Log> instead of raw pointers, and statement/query factory signatures accept view-based names and SQL text rather than rvalue strings. Input views are consumed within Database and are not retained across the DLL boundary; owned text and bytes use Base Safe types. The exported layout of Database, PreparedSTMT, Row, Rows, Value, NamedValue and backend result containers was tightened to enforce DLL-safe ownership and out-of-line heap operations; consumers must recompile and update code that relied on old string, logger, or STL-owning ABI assumptions.
    • Breaking: Added shared telemetry state to exported Database and PreparedSTMT objects; rebuild consumers against this ABI revision.
    • Breaking: Value::Type::LongInteger and Value::Type::UnsignedLongInteger now store long long int and unsigned long long int, so they are 64-bit on every platform; use Get<long long int>() / Get<unsigned long long int>(). long int and unsigned long int are still accepted when constructing values.
    • Serialized operations on each built-in connection. RAII transactions hold exclusive connection access through commit or rollback and must remain on their creating thread.
  • Telemetry — Added thread-safe operation counts, success/failure totals, returned-row counts, latency aggregates, backend error/warning categories, retained StormByte::Safe::Shared snapshots, and StormByte::Safe::String / std::string flattening for SQLite, PostgreSQL and MariaDB. Database telemetry derives from StormByte::Telemetry and uses independent best-effort Clock::Sample measurements, removing obsolete per-category locks and cumulative-time subtraction. Same-category samples can overlap or nest, and clock snapshots use GetValues(). Concurrent readers see zero rather than an uninitialized minimum-latency sentinel while the first result is being published.
  • Build and distribution — Ported the library to BuildMaster 2 HOST with shared/static selection. Static consumers receive flattened private vendor dependencies; vendor archives do not need repacking. Updated Doxygen configuration for StormByte Base and Logger 2.0 and the dual-license terms. Dependency tags and generated cross-links use verified HTTPS endpoints; preprocessing recognizes the Safe declaration and caller-inline macros. Doxygen generation was checked with warnings treated as errors without persisting that validation policy in CMake. Restored Linux CI coverage for Clang/libc++ with explicit -stdlib=libc++ in OFF and BUNDLED dependency modes; SYSTEM remains excluded for that variant to avoid mixing standard-library ABIs.
  • Robustness tests — Expanded tests for numeric boundaries, Row/Rows value semantics, backend scalar and binary round-trips, transaction rollback, prepared-statement failures, registry duplicates and cleanup with long and embedded-NUL names, same-connection concurrency, overlapping telemetry samples, Safe classification, and an installed external consumer using Safe collections and inherited SQLite path constructors. Regression tests preserve complete embedded-NUL text through value/row copies, Safe collections and SQLite bindings, reject invalid SQLite SQL and paths, and reject PostgreSQL NUL text without inserting a truncated prefix. Telemetry assertions now use fixed-width unsigned expected values and SQLite concurrency lambdas omit unnecessary captures, allowing strict warning validation without suppressions.

Fixed

  • MSSQL backend — Fixed result and statement handling across FreeTDS versions:
    • Zero-length text and binary values are returned as empty values instead of being padded by dbconvert().
    • Connections enable QUOTED_IDENTIFIER, so double-quoted identifiers resolve as identifiers on older DB-Library releases.
    • NULL prepared-statement parameters are sent as untyped NULL, allowing them in any column type such as VARBINARY(MAX).
    • SQL Server error messages are kept instead of DB-Library's generic notice, and Telemetry::Errors() now counts them.
  • Windows bundled OpenSSL consumers — Nested builds now link ws2_32 and crypt32 alongside the static bundled OpenSSL:
    • PostgreSQL's Meson configure, so its OpenSSL function checks succeed.
    • MariaDB Connector/C plugin DLLs such as sha256_password.dll.
  • TLS dependency selection — Added WITH_OPENSSL=SYSTEM|BUNDLED, rejecting OFF and retaining BUNDLED as the default. Windows forces BUNDLED regardless of the requested value, matching its database client policy. Bundled FreeTDS, MariaDB Connector C and PostgreSQL share pinned static OpenSSL 3.5.9 in bundled mode or discover installed dynamic OpenSSL in system mode without requiring static archives. CMake clients receive the selected library and include paths with static discovery disabled for SYSTEM; PostgreSQL uses native Meson discovery without a generated pkg-config adapter. Changing dependency modes requires a clean build directory. Linux and macOS CI select OpenSSL to match enabled dependency modes and omit the option when backends are OFF; Windows CI explicitly selects BUNDLED, and macOS only adds system OpenSSL search paths in SYSTEM jobs. The installed-consumer smoke test checks that bundled TLS clients using SYSTEM resolve the selected SSL and Crypto dynamic libraries, rather than silently falling back to a different installation.
  • MSSQL behavior tests — Query the fixture's temporary tables with SQL Server syntax, distinguish empty values from SQL NULL using DB-Library indicators, use the MAX binary RPC type, and set the text-size limit so...
Read more

Version 1.1.0

Choose a tag to compare

@StormBytePP StormBytePP released this 13 Sep 19:53

[Summary]

StormByte Database is the C++26 SQL layer of the StormByte suite.

One API covers SQLite, PostgreSQL and MariaDB.
Backends are base classes: you derive your schema, prepare statements and hook connect there.
This repository is not Base, Buffer, Config, Crypto, Logger, Multimedia, Network or System.
It requires StormByte Base 1.1.0 and StormByte-Logger 1.1.0 or newer.

If you landed here from a release link and have not read the tree:

  • What this module is, how to build it, and short examples: README.md
  • License: GNU Lesser General Public License version 3 or later, LICENSE

Fixed

  • Backend connection and transaction handling
    • Fixed system connector discovery with WITH_SQLITE=SYSTEM, WITH_POSTGRES=SYSTEM and WITH_MARIADB=SYSTEM.
    • Fixed ownership transfer when moving connected SQLite, PostgreSQL and MariaDB backends.
    • Fixed transactions silently continuing after failed BEGIN or COMMIT commands.
    • Fixed PostgreSQL connection handling for credentials containing quotes or backslashes.
  • Prepared statements and result handling
    • Fixed PostgreSQL and MariaDB numeric result parsing so invalid values return query errors instead of silent zero values.
    • Fixed PostgreSQL prepared statements with multiple text or numeric parameters.
    • Fixed SQLite prepared statements truncating unsigned integer values.
    • Fixed MariaDB prepared statements interpreting unsigned integers as negative values.
  • Fixed Row index access to throw the Database OutOfBounds exception.

Changed

  • Updated the minimum requirements to StormByte Base 1.1.0 and StormByte-Logger 1.1.0, including component-aware Database exceptions.
  • Adopted StormByte Base type concepts for Database value conversions.

Version 1.0.0

Choose a tag to compare

@StormBytePP StormBytePP released this 04 Sep 23:06

[Summary]

StormByte Database is the C++26 SQL layer of the StormByte suite.

One API covers SQLite, PostgreSQL and MariaDB.
Backends are base classes: you derive your schema, prepare statements and hook connect there.
This repository is not Base, Buffer, Config, Crypto, Logger, Multimedia, Network or System.

If you landed here from a release link and have not read the tree:

  • What this module is, how to build it, and short examples: README.md
  • License: GNU Lesser General Public License version 3 or later, LICENSE

Initial public release of StormByte Database.

Added

  • Database abstract connection: Connect / Disconnect, Query / SilentQuery, named prepared statements, isolation and RAII transactions
  • Inheritance-oriented backends — SQLite3, MariaDB and Postgres with protected constructors
  • Value — type-erased SQL cell (NULL, integers, double, text, blob, bool) with safe Get<T>()
  • NamedValue, Row, Rows — column lookup by name or index
  • PreparedSTMT — positional binds (0-based), nullptr is SQL NULL, ExpectedRows on execute
  • Transaction — rolls back if neither Commit nor Rollback ran
  • SslMode for MariaDB and PostgreSQL (SQLite ignores it)
  • IsolationLevel mapped per backend
  • Optional backends: WITH_SQLITE / WITH_POSTGRES / WITH_MARIADB as OFF, SYSTEM or BUNDLED
  • Exception types: ConnectionError, WrongValueType, ColumnNotFound, OutOfBounds, QueryException, UnknownSTMT, ExecuteError

Notes

  • First stable release of StormByte Database.
  • Not thread-safe: one connection per thread.
  • Needs a C++26 compiler and CMake ≥ 3.28.