ScalarDB Files

Summary

This release includes several improvements and bug fixes.

Community edition

Improvements

• Replaced MySQL Connector/J with MariaDB Connector/J due to licensing concerns. (#3428)
• Inserting or updating records with TIME (microsecond precision), TIMESTAMP (millisecond precision), and TIMESTAMPTZ (millisecond precision) column values will truncate out-of-range precision rather than throwing an exception. (#3393)
• Shortened JDBC index names using a hash when they exceed the maximum identifier length supported by the underlying database. (#3481)

Bug fixes

• Upgraded the Netty library to fix security issues: CVE-2026-33870 and CVE-2026-33871 (#3452)

Enterprise edition

Improvements

ScalarDB SQL

• Update the TIMESTAMPTZ literal to make optional the space character before the UTC timezone Z character. For example, 2021-03-04 12:30:45.123Z is now accepted, in addition to the current format 2021-03-04 12:30:45.123 Z. Also, when selecting a TIMESTAMPTZ column, the value is printed without a space before the Z.
• Fixed an issue where the shadow jar was unnecessarily published to GitHub Packages for the CLI module.
• Inserting or updating records with TIME (microsecond precision), TIMESTAMP (millisecond precision), and TIMESTAMPTZ (millisecond precision) column values will truncate out-of-range precision rather than throwing an exception.

Bug fixes

ScalarDB Cluster

• Upgraded grpc_health_probe to fix security issues: CVE-2025-59250 and CVE-2026-25679
• Upgraded the Netty library to fix security issues: CVE-2026-33870 and CVE-2026-33871
• Upgraded grpc_health_probe to fix a security issue: CVE-2026-34986.

ScalarDB SQL

• Fixed a bug where duplicate column names were allowed in CREATE TABLE statements.
• Fixed missing strict date validation on time-related type formatters, which could allow invalid dates (e.g., February 30) to be silently accepted instead of rejected.