minhphien / migratordotnet

Automatically exported from code.google.com/p/migratordotnet
0 stars 0 forks source link

Add function to get list of available migrations #64

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
For testing purposes it would be useful to be able to get a list of all
available migrations. The function would work similar as the one that
returns the list of the applied migrations.
For example, it would help testing migration between the latest and
previous version - right now, as I understand it, it is necessary to hard
code the migration numbers.

Original issue reported on code.google.com by tom...@gmail.com on 2 Sep 2008 at 12:48

GoogleCodeExporter commented 9 years ago
All unapplied migrations?
How does the 'dry run' option from Issue #52 work for this? Would you like 
something 
else?

Original comment by geoffl...@gmail.com on 5 Sep 2008 at 10:47

GoogleCodeExporter commented 9 years ago

Original comment by geoffl...@gmail.com on 5 Sep 2008 at 10:48

GoogleCodeExporter commented 9 years ago
It might help too, although I had something a bit different on mind:
a generic unit test that migrates the db to the latest version (possible with 
current
API), then goes through migrations 1 to (latest-1) and tries to migrate to that 
and
back to latest, each time saving the db schema and doing an Assert on it being 
the
same before and after migrating back and forth.
The issue I saw was that there was no way to find out the value of (latest-1).

Original comment by tom...@gmail.com on 8 Sep 2008 at 1:14