Skip to content

5.1.0 (yanked)

Choose a tag to compare

View all tags
@amunra amunra released this 30 Sep 14:40
· 6 commits to main since this release
5.1.0
b3f08fa
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Yanked release

There are no reported bugs, but this release has some behaviour and usability inconsistencies with nanoseconds behaviour and 9.1.0 in what precision is used by the server for messages sent by the client between the designated timestamp and other timestamp columns behaving differently. We will release 6.0.0 shortly which will make using nanosecond timestamps more consistent.

Overview

This is a very small release which adds support for nanosecond-precision columns.

Features

From QuestDB 9.1.0 you can use CREATE TABLE SQL statement with TIMESTAMP_NANO column types,
and/or configure the database to use nanosecond precision designated timestamp columns by setting the line.timestamp.default.column.type=TIMESTAMP_NANO config option in server.conf.

This client release adds support for sending timestamps to the server without loss of precision.

The change is backwards compatible with older QuestDB versions and does not introduce new APIs.

Full Changelog: 5.0.0...5.1.0

Assets 2
Loading