-
Notifications
You must be signed in to change notification settings - Fork 78
Number sequence option #16
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
Number sequence option #16
Conversation
* SCM coordinates * issue management * CI Management * distribution management
…efault for all of the templates. Now both "--//" and "-- //" are acceptable. "-- //" is a more standard way to use comments in standard sql. Now editors should not complain about our marker comments.
And add badges
Update maven xsd location Update parent Update clirr version Update mybatis Update derby Update hsqldb Update appassembler maven plugin Update deprecated basedir to project.basedir
migrations is simply migrations.
Refreshing build
…ex of the dot (.) to allow for dots in the change description.
junit to 4.12 appassembler-maven-plugin to 1.9
travis ci build for jdk8, update dependencies, and site page xsd.
…down-on-README Update README.md
…down-on-README Update README.md
Formatting changes
Formatting changes
…thro' special case of bootstrap.sql
…thro' special case of bootstrap.sql
…ber-sequence-option
@WalterPhillips Can you rebase and squash all the commits? |
Thank you for your contribution, @WalterPhillips ! I understand the needs, but there seems to be various needs and this is not generalized enough, IMO. Just an idea, but an option that takes a pattern string for java.text.DecimalFormat might be flexible. This PR is also a little bit messy, so please open a new PR if you are still interested in fixing this. |
Tracks sql scripts with sequential numbers instead of timestamp.
This addresses the non-timestamp sequence issue
e.g.
1_first_file.sql
2_second_file.sql