Google Cloud Spanner JDBC Driver version 1.1.6

Fix: Queries would run indefinitely if a connection URL with a non-existing instance or database was specified.

Google Cloud Spanner JDBC Driver version 1.1.5

v1.1.5

Update README.md

Google Cloud Spanner JDBC Driver version 1.1.4

spanner-jdbc-1.1.4

[maven-release-plugin] copy for tag spanner-jdbc-1.1.4

Google Cloud Spanner JDBC Driver version 1.1.1

Fixed the following issues:

• #105 Problem binding TIMESTAMP
• #110 DELETE in extended mode would fail when parameters were included in the query
• #112 Fixed potential ArrayOutOfBoundsException when setting parameters

Google Cloud Spanner JDBC Driver version 1.1

Version 1.1

• Upgrade to Google Cloud Spanner Java client library 0.57.0-beta
• Added support for allow_commit_timestamp columns (https://cloud.google.com/spanner/docs/commit-timestamp)
• Changed when a query is actually executed on Spanner (see #75). Queries are now sent directly to Spanner when an execute(...) or executeQuery(...) method is called.

Google Cloud Spanner JDBC Driver version 1.0.13

• Added support for getting a key file from Google Cloud Storage
• Added support for using an emulator when connecting using a DataSource object

Google Cloud Spanner JDBC Driver version 1.0.12

• Fixed several issues that could cause exceptions when getting ResultSetMetaData for queries with Cloud Spanner specific functions or expressions.

Google Cloud Spanner JDBC Driver version 1.0.10

• Fixed issues #81 and #82 .

Google Cloud Spanner JDBC Driver version 1.0.9

• Fixed issues #73, #76 and #77
• Made host and project id configurable for the test cases, in order to be able to run all tests against both a real Cloud Spanner instance and against a Cloud Spanner Emulator.

Google Cloud Spanner JDBC Driver version 1.0.8

• Added support for Cloud Spanner Emulator (https://github.com/olavloite/spanner-emulator-tester)
• Fixed issues #65 and #68
• Fixed an issue where an aborted transaction could cause ResultSet#next to throw a SpannerException instead of a SQLException