Output to sql file instead of commiting against the DB

[flyway]

Original author: sylvain....@gmail.com (March 18, 2013 05:59:16)

HI,

We're just starting to use flyway in our project and so far it looks really good. It's gonna help us a lot automatically upgrade all of our different environments.

One thing that would be nice is way to combine all or specific sql versions into one sql file. We would use this because we can't tell our client's IT department (big client) to use flyway for upgrading the prod database and we obviously don't have access to that database.
Currently the only way we can get the database upgraded is by sending them an SQL file (which they run on their stage before prod).

In theory we could manually combine all the relevant files ourselves but that could be a bit cumbersome and error-prone. Also things like placeholders would need to be replaced manually (search & replace but still) with the proper value, again error-prone.

We use maven so a new goal should do it.

That said thanks for the great work!

Original issue: http://code.google.com/p/flyway/issues/detail?id=452

[flyway]

From axel.fontaine.business@gmail.com on March 18, 2013 17:13:10
Hi Sylvain,

thanks for your suggestion! This is the current state of affairs: http://stackoverflow.com/questions/15447276/previewing-the-sql-statements-before-migration-using-flyway

Cheers
Axel

[flyway]

From sylvain....@gmail.com on March 18, 2013 19:32:43
Thanks Axel, very excited about this. I wish I had time to help.

[aldas]

+1

[kerryland]

+1

[RalphEng]

+1

[pimlottc]

+1

[ghost]

+1

[imsandli]

any news about this?
This feature would be really nice to have.

[danijelst]

+1

[jezs]

I'd love to have this feature as well.

[roboll]

is this still on the roadmap somewhere?

[edgedalmacio]

+1

[manikantag]

+1

[abhinavrau]

+1

[jmisur]

+1.
btw why is this 1 year old issue (having so many +1s and 3 closed duplicates) preceded by some less "popular" issues in the milestone planning?

[trautonen]

+1

This is also relevant when you have a lot of migrations. Running 100+ migrations to run an integration test is just too slow. Flyway should be able to check the current version of the db to be updated and then combine the remaining migrations to run at once in single transaction. This of course might get tricky if you are using also programmatic migrations. Maybe sneaking in to the jdbc driver what sql clauses are getting executed and grab them. Or some other solution that is not this hackish. This would also allow proper reporting features of the migrations.

[axelfontaine]

I just wanted to give you a heads up that this issue is still on the roadmap.
Implementing it requires introducing some new abstractions to decouple execution from jdbc.

The reason it hasn't been prioritized higher than it was, is simply that other features were more relevant and that as a general rule bugs get fixed before new features.

P.S.: If this feature is an urgent need for your organisation, you do also have to option to sponsor its development to get it done much sooner: http://flywaydb.org/support/sponsor.html

[PeeZu]

+1

[vbazagad]

+1

[neylorsousa]

+1

[alxmrtn]

+1

[deusaquilus]

+1

[trumpetx]

+1

[chris03]

+42

[trumpetx]

Hey everyone with a +1, I could use some help validating my implementation of "Dry Run". Did I miss anything?

#1458

[cleverdeveloper]

I would be happy to test it, but so far having difficulties to build it with or without your pull request.

[trumpetx]

@cleverdeveloper - that was my biggest challenge when changing the code, here's how to build by skipping tests:

mvn install -P-CommercialDBTest -P-CommandlinePlatformAssemblies -DskipTests=true

Once built, the version will be 0-SNAPSHOT if I recall correctly...

[cleverdeveloper]

I am in the process of trying it out, but I wonder if it does output to file as it says in the title or this would be a next step to implement?

[trumpetx]

You know what, I didn't implement the fix to this issue exactly... interesting. I found another issue which was closed as a duplicate of this issue and I guess I sort of just implemented the other one. This quite simply runs a "dry run" (using transactions) against a database to test upgrades before they happen. I guess maybe I should open a new issue that's distinct from this one (or reopen the other one)

[dennisjansen]

+1

[who]

+1

[thebhushanp]

+1

[myhau]

+1

[akikhtenko]

+1

[lichnost]

+1

[odinsy]

+1

[ligasgr]

+1

[shoutcool]

this issue is a show-stopper for using flyway in production environments

[zeidlermicha]

+1

[marbon87]

+1

[rvillars]

+1

[agusmba]

Maybe using log4jdbc or one of its more recent forks?.

You'd need a copy of the staging/production database though (at least its schema and flyway tables...)