Version history

Version 3.15.1, released 2022-05-05

Bug fixes

  • Make SpannerTransaction pick up SpannerConnection.LogCommitStats as documented. (commit db5c55d)

Version 3.15.0, released 2022-05-04

New features

  • Make ephemeral transactions retry on abort. (commit 97faf1c)
  • Introduced SpannerDate struct for date-only values. (The default type for DATE columns is still DateTime.) (commit 4e3b94e)
  • Introduced PgNumeric struct for support of the NUMERIC data type in the Postgres dialect. (commit 87c3306)

Version 3.14.0, released 2022-03-28

New features

Version 3.13.0, released 2021-12-01

Version 3.12.0, released 2021-08-24

  • Commit 7c6a6f1: feat: add support for JSON data type in Spanner (issue 6390)
  • Commit ac367e2: feat: Regenerate all APIs to support self-signed JWTs
  • Commit 61938b6:
    • feat(Spanner): Support comments and statement hints in untyped commands.
    • Alternative to issue 6848
    • Closes issue 6847
  • Commit d26b04c: fix: address review comments
  • Commit d2025be: fix: use logger from SpannerSettings
  • Commit b34f6f4: cleanup: fix comment + remove unnecessary import
  • Commit fc7a41b: test: remove connectionstring tests and add settings test
  • Commit 6016ef0:
    • feat: support custom SpannerSettings in SessionPoolManager
    • Support setting custom SpannerSettings when creating a SessionPoolManager.
  • Commit 0ab6b8b:
    • feat: allow adding an additional version header
    • Allows adding an additional version header to the connection string. This will be
    • added to the x-goog-api-client header that is used by the underlying Spanner client.
    • Only a fixed set of values may be set for the header (currently only 'efcore' is
    • allowed), and the property is not intended for public use.
  • Commit 250124f:
    • fix: synchronize access to the underlying transaction for ambient transactions (issue 6616)
      • fix: synchronize access to the underlying transaction for ambient transactions
    • Synchronizes access to the underlying Spanner transaction to prevent
    • multiple transactions from being created if parallel commands are
    • executed on the ambient transaction.
      • test: add integration test
      • fix: use Lazy for initialization
      • chore: address review comments
      • fix: remove unnecessary read call

Version 3.11.0, released 2021-07-09

Version 3.10.0, released 2021-06-28

Version 3.9.0, released 2021-06-09

  • Commit 0fb438e: feat: add query_optimizer_statistics_package support (see below)

The optimizer statistics package can be set through QueryOptions, which can be configured through the following mechanisms:

  • At the SpannerConnection level.
  • Through the SPANNER_OPTIMIZER_STATISTICS_PACKAGE environment variable.
  • At a query level.

If the options are configured through multiple mechanisms then:

  • Options set at an environment variable level will override options configured at the SpannerConnection level.
  • Options set at a query-level will override options set at either the SpannerConnection or environment variable level.

If no options are set, the optimizer statistics package will default to the package the database is pinned to. If the database is not pinned to a specific package, then the Cloud Spanner backend will use the "latest" version.

Version 3.8.0, released 2021-05-18

Version 3.7.0, released 2021-04-01

Version 3.6.0, released 2021-03-17

Version 3.5.0, released 2021-02-08

Version 3.4.0, released 2020-12-14

  • Commit 9fb3e43: feat: Database Admin: Adds UpdateDatabaseDdlMetadata.Throttled to indicate when a DDL operation is throttled due to resource constraints.

Version 3.3.0, released 2020-10-01

Version 3.2.0, released 2020-09-10

Version 3.1.0, released 2020-07-14

Version 3.1.0-beta01, released 2020-06-16

  • Commit 5b07f5a: fix: Roll back uncommitted (and not-rolled-back) read/write transactions on session release
  • Commit 7de296c: fix: Workaround for emulator bug of not populating ExecuteBatchDmlResponse.status
  • Commit a4455b9: feat: Spanner emulator support in Google.Cloud.Spanner.Data
  • Commit 947a573: fix: Regenerate all clients with more explicit documentation
  • Commit 0b01e4b: feat: add support for spanner emulator detection in clients (issue 4928)

Note that while the SpannerNumeric type has been added to the Google.Cloud.Spanner.V1 library, it is not currently integrated with the rest of the code, and should be ignored at this time.

Version 3.0.0, released 2020-04-15

GA release targeting GAX 3.0.0. No new features compared with 3.0.0-beta02, other than small resource name improvements for backups.

Version 3.0.0-beta02, released 2020-03-18

  • Commit c5090d1:
    • feat: Adds the ability to set QueryOptions when running Cloud Spanner queries.
  • Commit 36f1e1e: Apply gccl header for Spanner clients in Google.Cloud.Spanner.Data
  • Commit f21fd27:
    • feat: Backup support in Database Admin API
    • feat: List operations RPC in Database Admin API

This release depends on the GA version of GAX 3.0.

Version 3.0.0-beta01, released 2020-02-18

This is the first prerelease targeting GAX v3. Please see the breaking changes guide for details of changes to both GAX and code generation.

Version 2.1.0, released 2019-12-12

  • Commit 0740a76: Adds support for retriable transactions
  • Transparent support for batch creation of sessions (to make session creation more efficient)

Version 2.0.0, released 2019-06-03

New features:

  • Batch query support
  • Connection string option to enable SpannerDataReader.GetSchemaTable() to return schema information
  • DML and PDML support
  • Batch DML support
  • Session label support

Breaking changes:

  • Many aspects of configuration have changed. Please refer to the configuration guide, migration guide and connection string options for more details.
  • Null values are returned as DBNull.Value by default rather than the CLR default value for the type. Array and struct elements use a null value where feasible, but throw InvalidCastException when requested to be converted to a non-nullable value type. The 1.0 behavior can be requested using the UseClrDefaultForNull connection string option.
  • Hashtable is no longer used as a default type for struct values. It can still be specified explicitly. The new default is Dictionary<string, object>.
  • The libraries no longer target netstandard1.5; only netstandard2.0 and net45 are supported

Version 1.0.0, released 2017-12-05

Initial release.