mirror of
https://github.com/status-im/migrate.git
synced 2025-02-23 16:28:08 +00:00
748ae8f06a
Support for Google Cloud Spanner, closes #172. Includes example migrations ported over from the PostgreSQL driver. In all examples provided by Google I’ve come across, camel-case is used for table names, columns, etc. Hence the examples use this naming convention.
29 lines
1.2 KiB
Markdown
29 lines
1.2 KiB
Markdown
# Google Cloud Spanner
|
|
|
|
## Usage
|
|
|
|
The DSN must be given in the following format.
|
|
|
|
`spanner://projects/{projectId}/instances/{instanceId}/databases/{databaseName}`
|
|
|
|
See [Google Spanner Documentation](https://cloud.google.com/spanner/docs) 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.
|
|
>
|
|
> ```log
|
|
> 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) |