Skip to content

Releases: googleapis/nodejs-spanner

v1.0.0

13 Jan 00:40
0ff81ca
Compare
Choose a tag to compare

General Availability

The Spanner library is now considered to be General Availability (GA). This means it is stable; the code surface will not change in backwards-incompatible ways unless absolutely necessary (e.g. because of critical security issues) or with an extensive deprecation period. Issues and requests against GA libraries are addressed with the highest priority.

Breaking change

toJson() will not wrap integers and floats into objects by default. Example of the change in the JSON returned by toJson():

 {
   "boolValue": false,
   "stringValue": "Hello",
-  "intValue": {
-    "value": "42"
-  },
+  "intValue": 42,
-  "floatValue": {
-    "value": "3.14"
-  }
+  "floatValue": 3.14
 }

You can still ask toJson() to wrap numbers by providing an option object to toJSON() specifying wrapNumbers: true. You should do it if you expect that you will work with integers greater than Number.MAX_SAFE_INTEGER, as toJSON() will throw an exception if asked to convert an integer when it's not safe to do that without losing precision. See #80 for details.

Fixes

  • (#2644) Increased timeout to match timeout in config file
  • (#18) Spanner library should have a way to track leaked sessions
  • (#78) SessionPool acquireQueue concurrency limit causes sessions to pile up under load
  • (#80) RowBuilder.toJSON should return un-wrapped Floats and Ints

@google-cloud/spanner v0.10.0

15 Dec 22:42
f5d7b76
Compare
Choose a tag to compare

Deprecation Notice

This release deprecates the date, time and timestamp instance methods. Please use the static methods in their place.

Bugfixes

  • (#61): setInterval causes process to hang.

@google-cloud/spanner v0.9.0

07 Dec 23:57
929af6c
Compare
Choose a tag to compare

Features

  • (#19): rate limit session creations/deletions
  • (#26): emit session errors on database objects

Bugfixes

  • (#13): keep-alive not functioning properly
  • (#25): properly handle idle resources

@google-cloud/spanner v0.8.2

07 Dec 16:59
Compare
Choose a tag to compare

release level

Bugfixes

(#56): Un-promisify transaction mutation methods. (Thanks, @WaldoJeffers!)

@google-cloud/spanner v0.8.1

22 Nov 22:31
c9c3d35
Compare
Choose a tag to compare

release level

Bugfixes

  • Fixed a bug where the client library did not properly handle query parameter types. (#42, #43)

Refer to the nodejs-spanner API reference documentation for details.

@google-cloud/spanner v0.8.0

27 Oct 18:35
Compare
Choose a tag to compare

release level

Features

  • Support for Application Default Credentials (#8)

Bugfixes

  • Fixed a bug where the client library did not automatically retry in some cases. (#12)

Implementation Details

  • Change to a new linter (ESLint) and code style formatter (prettify).
  • Update docs to use JSDoc 3.
  • Migrate to the googleapis/nodejs-spanner repository.

Refer to the nodejs-spanner API reference documentation for details.

@google-cloud/spanner v0.7.1

24 Oct 15:12
Compare
Choose a tag to compare

release level

Implementation Details

  • Remove google-proto-files dependency.
  • Update @google-cloud/common-grpc dependency.

@google-cloud/spanner v0.7.0

24 Oct 05:01
Compare
Choose a tag to compare

release level

Beta Release

@google-cloud/spanner is now in the beta release level. Libraries defined at the Beta quality level are expected to be mostly stable, while we work towards their release candidate. We will address issues and requests with a higher priority.

@google-cloud/spanner v0.6.0

24 Oct 04:58
Compare
Choose a tag to compare

release level

Bugfixes

  • Database instances are now cached so sessions can be re-used. (#2362))

@google-cloud/spanner v0.5.0

24 Oct 04:56
Compare
Choose a tag to compare

release level

Features

  • Introduce getTransaction, allowing more natural Promise usage in a transaction workflow. (#2344)

Bugfixes

  • Properly close a request stream in the event of an error. (#2358)
  • Update parameters under which requests are retried. (#2390)
  • Properly handle multi-row mutations with heterogeneous columns; h/t @jscinoz. (#2426)