Skip to content

Releases: ydb-platform/ydb-go-sdk

v3.118.1

06 Nov 12:41

Choose a tag to compare

  • Fixed connection timeout issue in topics writer
  • Supported sql.Null* from database/sql as query params in toValue func

Full Changelog: v3.118.0...v3.118.1

v3.118.0

30 Oct 20:17

Choose a tag to compare

  • Added support for nullable Date32, Datetime64, Timestamp64, and Interval64 types in the optional parameter builder
  • Added method query.WithIssuesHandler to get query issues

Full Changelog: v3.117.2...v3.118.0

v3.117.2

29 Oct 10:07

Choose a tag to compare

  • Added support for Result.RowsAffected() for YDB database/sql driver
  • Upgraded minimal version of Go to 1.23.9
  • Fixed race in readerReconnector

Full Changelog: v3.117.1...v3.117.2

v3.117.1

07 Oct 22:18

Choose a tag to compare

  • Fixed scan a column of type Decimal(precision,scale) into a struct field of type types.Decimal{} using ScanStruct()
  • Fixed race in integration test TestTopicWriterLogMessagesWithoutData
  • Fixed traces handling in topic.Reader

Full Changelog: v3.117.0...v3.117.1

v3.117.0

04 Oct 06:05

Choose a tag to compare

  • Fixed conn/pool.Get() behaviour for YDB databases with public IPs. Bug was introduced in v3.116.2
  • Added helper methods log.WithFields and log.FieldsFromContext for working with structured logging fields via context.
    These methods allow adding custom fields to the context, which are later extracted by the logger.

Full Changelog: v3.116.4...v3.117.0

v3.116.4

01 Oct 13:39

Choose a tag to compare

  • Fixed error handling in internaltopicreader.addOnTransactionCompletedHandler

Full Changelog: v3.116.3...v3.116.4

v3.116.3

28 Sep 08:57

Choose a tag to compare

  • Default grpc message size adjusted to the server's defaults

Full Changelog: v3.116.2...v3.116.3

v3.116.2

25 Sep 09:08

Choose a tag to compare

  • Fixed grpc connections leak on reused node IP

Full Changelog: v3.116.1...v3.116.2

v3.116.1

22 Sep 17:34

Choose a tag to compare

  • Fixed an issue where topic.UpdateOffsetsInTransaction was executed on a node different from the one where the transaction was running, which could lead to the error "Database coordinators are unavailable"

Full Changelog: v3.116.0...v3.116.1

v3.116.0

15 Sep 13:30

Choose a tag to compare

  • Added experimental support for query results in Apache Arrow
  • Fix flaky unit test TestUnboundedChanContextTimeout

Full Changelog: v3.115.7...v3.116.0