History

Lukas Joergensen 480a5a634a postgres: Move lock out of ensureVersionTable, for consistency with other SQL operations (#173 ) * Consistently lock in ensureVersionTable and do not call ensureVersionTable from Drop across all database implementations * Add test for dropping postgres databases * Fix failing database tests * Fix CockroachDb test, lock table should be created before versionTable * Add Initialize() to Driver interface, and add integration tests for Drop() between database implementations and migrate * Remove Initialize, document breaking behaviour of Drop * Revert introduction of Initialize method * Removed Initialize in Stub as well * Remove call to non-existent Initialize and make sure to close re-initialized database connections * Revert changes to TestDrop in database/testing * Split Test and TestMigrate into different test entrypoints * Remove unused import in migrate_testing * Remove erroneous code to fix tests * Add stub source imports to database tests * Add Stub source to migrate tests * Use example migrations for tests * Add file driver to database tests * Align database directory layout * Add file source driver to Cassandra * Review changes * Minor syntactic change for cleaner diff		2019-02-26 15:56:57 -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	postgres: Move lock out of ensureVersionTable, for consistency with other SQL operations (#173 )	2019-02-26 15:56:57 -08:00
spanner_test.go	postgres: Move lock out of ensureVersionTable, for consistency with other SQL operations (#173 )	2019-02-26 15:56:57 -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.