Issue 247 in flyway: absolute path to sql migrations

[fly...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 247 by kaczanow...@gmail.com: absolute path to sql migrations
http://code.google.com/p/flyway/issues/detail?id=247

It would be convenient to pass an absolute path to sql patches (right now
flyway takes only relative path, which is cumbersome in some scenarios).
Could you enhance flyway to implement it?

[fly...@googlecode.com]

Comment #1 on issue 247 by axel.fontai...@gmail.com: absolute path

to sql migrations
http://code.google.com/p/flyway/issues/detail?id=247

Hi Tomek,

right now Flyway loads all migrations from the classpath. Am I correct if I
understand that you would also like to option to load migrations from
arbitrary locations on the filesystem?

Cheers
Axel

[fly...@googlecode.com]

Comment #2 on issue 247 by kaczanow...@gmail.com: absolute path to sql
migrations
http://code.google.com/p/flyway/issues/detail?id=247

yes, this is exactly what I would like to have

--
Regards / Pozdrawiam
Tomek Kaczanowski
http://practicalunittesting.com

[fly...@googlecode.com]

Comment #3 on issue 247 by luke.car...@tdm.info: absolute path to sql
migrations
http://code.google.com/p/flyway/issues/detail?id=247

I'd be extremely interested in this feature, but my lack of experience of
Maven is making attempting to implement it extremely difficult. At present,
it's not really feasible to use Flyway with a non-Java project, but if it
were able to load migrations from a directory on the filesystem it'd be
perfect.

[fly...@googlecode.com]

Comment #4 on issue 247 by luke.car...@tdm.info: absolute path to sql
migrations
http://code.google.com/p/flyway/issues/detail?id=247

Would something like this be suitable? I'm aware of the formatting
inconsistencies and have only done minimal testing thus far. Feedback much
appreciated!

https://github.com/LukeCarrier/flyway/commit/decc0e61e2798388aa816d7e30db5409625f5695

[fly...@googlecode.com]

Comment #5 on issue 247 by axel.fontai...@gmail.com: absolute path

to sql migrations
http://code.google.com/p/flyway/issues/detail?id=247

Hi Luke,

thanks for your contribution. Yes, a "file:" prefix is the direction I
would favor. I do however not understand what you mean with not really
feasible to use Flyway with a non-Java project. Doesn't the command-line
tool help? How exactly does your scenario look like?

Cheers
Axel

[fly...@googlecode.com]

Comment #6 on issue 247 by luke.car...@tdm.info: absolute path to sql
migrations
http://code.google.com/p/flyway/issues/detail?id=247

Hi Axel,

The issue we faced with Flyway was that it just didn't work in a way that'd
be suitable for us. As a PHP shop, it'd be impractical to package our
migrations into Java archives. That was really the only issue we ran into
with Flyway within our organisation!

As for the command line tool, we're using a tool called Phing
(http://www.phing.info/) to handle application deployment and testing.
We're in the process of polishing off some tasks so we can better automate
database migrations via Flyway. I'm sure we'd be happy to contribute these
too if you're interested?

Incidentally, I reformatted the changes and have attached a patch for them.
There's a good web interface for viewing them on GitHub, over here:
https://github.com/LukeCarrier/flyway/compare/74d95e6103524796e60c3bcb81af7d06642fec88...947e8ecb45bd2672192a9726624bd11277cd9671

Thanks for your time!

Attachments:
flyway-247.patch 15.4 KB