Reduce need for script duplication when adding support for a new database type [DATAJDBC-537]

[spring-projects-issues]

Mark Paluch opened DATAJDBC-537 and commented

Currently, we're required to duplicate and adapt several scripts (a schema file per integrationtest) if we decide to add support for a new database. We should revisit this arrangement to investigate on alternatives. Ideally, we can describe schema objects in a vendor-neutral way and then generate scripts by considering vendor-specifics.

One idea could be the use of Liquibase change files or the direct use of the Liquibase API to generate schema objects. We should consider this change in the light of DATAJDBC-536

---

Issue Links:

• DATAJDBC-536 Schema generation