Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify validate javadoc #1312

Closed
cowwoc opened this issue May 17, 2016 · 3 comments
Closed

Clarify validate javadoc #1312

cowwoc opened this issue May 17, 2016 · 3 comments
Labels
Milestone

Comments

@cowwoc
Copy link

@cowwoc cowwoc commented May 17, 2016

What version of Flyway are you using?

4.0.1

What database are you using (type & version)?

MySQL 5.6

What operating system are you using?

Windows 7

What did you do?

(Please include the content causing the issue, any relevant configuration settings, and the command you ran)
Flyway.migrate()

What did you expect to see?

Unable to resolve location classpath:db/migration

What did you see instead?

Build-time or runtime failure.

I want to throw an error if no migrations were found. This means either throwing an exception on my behalf if no migrations are found, or providing me a means to query how many SQL, Java migrations were found and letting me acting on it.

@cowwoc
Copy link
Author

@cowwoc cowwoc commented May 17, 2016

I suspect this feature would fit into Flyway.info().

@axelfontaine
Copy link
Contributor

@axelfontaine axelfontaine commented May 18, 2016

Flyway.validate() should be able to do this for you in case migrations have already been executed against the DB. Would that do the job for you?

@cowwoc
Copy link
Author

@cowwoc cowwoc commented May 18, 2016

The Javadoc for Flyway.validate() is very vague. What exactly "accidental changes" refer to? What does it check for? (and I suggest updating the Javadoc accordingly)

@axelfontaine axelfontaine changed the title RFE: Ability to detect if migrations are missing Clarify validate javadoc Jun 8, 2016
@axelfontaine axelfontaine added this to the Flyway 4.0.2 milestone Jun 8, 2016
axelfontaine added a commit to flyway/flywaydb.org that referenced this issue Jun 8, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.