YOJ 2.6.5 (Multiple table names for the same Entity)

• #32: Support multiple table names for the same Entity
  ⚠️ This is an Experimental API, which can change and/or disappear in any release.
  Use the new BaseDb.table(TableDescriptor) call in your Db to specify both Entity class and table name; the same is also supported by the new AbstractDelegatingTable(TableDescriptor) constructor.

YOJ 2.6.4 (improved logging for GRPC transport problems)

• #109: Use YDB Java SDK v2.3.7, with improved logging for GRPC transport problems

YOJ 2.5.12 (backport improved logging for GRPC transport problems)

Backport #109 to 2.5.x

• #109: Use YDB Java SDK v2.3.7, with improved logging for GRPC transport problems

YOJ 2.6.3 (bring back some deprecated YqlStatement ctors)

• #108: Bring back (as @Deprecated(forRemoval=true)) old ctors for MultipleVarsYqlStatement, PredicateStatement and YqlStatement

YOJ 2.6.2 (TableDescriptor refactorings)

• #32: TableDescriptor and related refactorings to make supporting multiple YDB tables under one YOJ Entity
• #95: Fix ClassCastException during initial schema check

YOJ 2.5.11 (backport TableDescriptor from 2.6.3)

Backport of v2.6.3, excluding FieldValue refactorings from v2.6.0.

YOJ 2.5.10 (Fix ClassCastException during initial schema check)

Backported to 2.5.x:

• #95 Fix ClassCastException during initial schema check

YOJ 2.6.1 (StdTxManager.useNewTxNameGeneration always enabled now)

• ca389b2 - StdTxManager.useNewTxNameGeneration field now does nothing and is deprecated for removal. It will be removed in YOJ 3.0.0.

YOJ 2.6.0 (FieldValue refactoring)

• #75: FieldValue is now a sealed interface in a dedicated package (<...databind>.values); old FieldValue is now also an interface and is deprecated. You'll get warning if you use old FieldValue's methods.
  • ⚠️ BREAKING CHANGE: FieldValue.get<Xxx>() methods are no longer there, not even in the deprecated old FieldValue interface. Please use FieldValue's sealed implementations' types with instanceof and switch pattern matching instead, e.g., if (value instanceof StringFieldValue strValue) { return strValue.str(); }
  • ⚠️ BREAKING CHANGE: Tuple-related types FieldValue.Tuple and FieldValue.FieldAndValue are now just Tuple and Tuple.FieldAndValue; and they were moved to a dedicated package (<...databind>.values)
  • Please use FieldValue's sealed implementations' constructors (e.g., new StringFieldValue("str")) instead of deprecated old FieldValue.of<Xxx>() methods
  • Please use FieldValue's sealed implementations' types in instanceof and switch pattern matching instead (if (value instanceof StringFieldValue str) { ... }, switch (value) { StringFieldValue str -> ...; }), instead of deprecated old FieldValue.is<Xxx>() methods

YOJ 2.5.9 (Update YDB SDK to v2.3.2)

• Update YDB SDK to v2.3.2 - 6ad68d2