You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 22, 2020. It is now read-only.
Be able to specify the names of "cassandra_migration_version*" tables in KeyspaceConfiguration or CassandraMigration
Table name prefix or suffix or full name can be specified
This allows multiple independent applications or modules share the same keyspace while all using cassandra-migration without interfering with each other
## Definition of Done
Table name prefix or suffix or full name can be specified in KeyspaceConfiguration or CassandraMigration, therefore,
Multiple migrations can be tracked in the same keyspace.
## Out of Scope
## How to Demo
1. Do migration with some .cql files on a keyspace
2. Do another independent migration with some other .cql files and different names of "cassandra_migration_version*" tables on the same keyspace
3. Check to confirm both migrations succeeded.
The text was updated successfully, but these errors were encountered:
james-hu
changed the title
capability to specify the name of "cassandra_migration_version*" table
Capability to specify the names of "cassandra_migration_version*" tables
Sep 28, 2016
Outcome Desired
Be able to specify the names of "cassandra_migration_version*" tables in
KeyspaceConfiguration
orCassandraMigration
## Definition of Done
Table name prefix or suffix or full name can be specified in
KeyspaceConfiguration
orCassandraMigration
, therefore,## Out of Scope
## How to Demo 1. Do migration with some .cql files on a keyspace 2. Do another independent migration with some other .cql files and different names of "cassandra_migration_version*" tables on the same keyspace 3. Check to confirm both migrations succeeded.
The text was updated successfully, but these errors were encountered: