History

Dale Hui f584949470 Update imports to reference fork. Thanks `make rewrite-import-paths`!		2018-01-19 10:56:55 -08:00
..
examples/migrations	Add example migrations	2017-06-05 10:50:14 +01:00
README.md	Skip test if SPANNER_DATABASE isn’t set	2017-06-20 17:53:41 +01:00
spanner.go	Update imports to reference fork.	2018-01-19 10:56:55 -08:00
spanner_test.go	Update imports to reference fork.	2018-01-19 10:56:55 -08:00

README.md

Google Cloud Spanner

Usage

The DSN must be given in the following format.

spanner://projects/{projectId}/instances/{instanceId}/databases/{databaseName}

See Google Spanner Documentation for details.

Param	WithInstance Config	Description
`x-migrations-table`	`MigrationsTable`	Name of the migrations table
`url`	`DatabaseName`	The full path to the Spanner database resource. If provided as part of `Config` it must not contain a scheme or query string to match the format `projects/{projectId}/instances/{instanceId}/databases/{databaseName}`
`projectId`		The Google Cloud Platform project id
`instanceId`		The id of the instance running Spanner
`databaseName`		The name of the Spanner database

Note: Google Cloud Spanner migrations can take a considerable amount of time. The migrations provided as part of the example take about 6 minutes to run on a small instance.
1481574547/u create_users_table (21.354507597s)
1496539702/u add_city_to_users (41.647359754s)
1496601752/u add_index_on_user_emails (2m12.155787369s)
1496602638/u create_books_table (2m30.77299181s)

Testing

To unit test the spanner driver, SPANNER_DATABASE needs to be set. You'll need to sign-up to Google Cloud Platform (GCP) and have a running Spanner instance since it is not possible to run Google Spanner outside GCP.