Support for database SQL bundled into release jar or dedicated database migration tooling

[bobbyrne01]

Hey, firstly great library! I've been testing it's features evaluating whether to integrate it into my project rather than Quartz and have a few questions around the database schema provisioning.

I see the README.md links to SQL in a test folder.

1. Is there any reason why the SQL is not bundled into the release .jar?

   Allowing consumers to reference the SQL from the classpath rather than having developers copy/paste the SQL duplicating it into their own projects.

2. Are there any recommendations for handling database schema upgrades?

   As-in, will upgrade SQL be provided if columns or keys are changed? or are we expected to drop and recreate everything each time?

3. Have you considered introducing a database migration tool? e.g Liquibase

   I know you probably don't want to enforce consuming projects to depend on Liquibase too but just curious on your thoughts

[kagkarlsson]

1. I have kept the scope of the project smaller, and left schema-migration/definition to users. Just to make things slightly easier. (for example, it is common to use separate users for DDL migrations and app)

2. Schema-migration requirements will be provided in upgrade notes. I suggest using Flyway or Liquibase for managing the schema. So far no schema-upgrades have required a recreate, I will intend to keep it that way.

3. Not really. It would have to be home-rolled I think, to avoid dependencies on third-parties