spring-projects / spring-projects/spring-data-relational
Reduce need for script duplication when adding support for a new database type [DATAJDBC-537]
@kurtn718 is already working on this.
Since Mar 30, 2023.
- Dominant language
- Java
- Stars
- 827
- Forks
- 394
- PR merge metrics
- No merged PRs in 30d
Description
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.