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

Does the plugin maintain the changelog #8

Open
GoogleCodeExporter opened this issue Jan 7, 2016 · 0 comments
Open

Does the plugin maintain the changelog #8

GoogleCodeExporter opened this issue Jan 7, 2016 · 0 comments

Comments

@GoogleCodeExporter
Copy link

I am planning to use this plugin and so had a very basic question about its 
usage - may be just a qucik FAQ to add.

Lets say, we have a existing database with pre-loaded data

1. Should we place Database dump @ - schema scripts i.e src/main/sql/schema


2. Everytime we run db-create it will override the database?


3. Let's suppose we need to add one more column in some x table, where should 
we keep that update x.sql script? I guess in update scripts i.e in 
src/main/sql/update ?

4. If yes, does everytime we run mvn db:update, it will execute all the scripts 
there? 

5. This will cause DB errors, like adding same column again and again?

6. Let's suppose we need to add more seed-data in some x table, where should we 
keep that x-data.sql? I guess in data scripts i.e in src/main/sql/data?

7. If yes, will same problem as 4 & 5 will occur again?


In nutshell, does the plugin maintain the changelog or handle what is updated 
and what is not? So that next time goal runs nothing fails?

I would love to use this plugin and try if I get above usage explained.

Original issue reported on code.google.com by [email protected] on 23 Apr 2015 at 6:16

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant