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

Consistent incrementer arrangement for PostgreSQL, DB2 and SAP HANA [SPR-16558] #21101

Closed
spring-projects-issues opened this issue Mar 6, 2018 · 0 comments
Assignees
Labels
in: data status: backported type: enhancement
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

@spring-projects-issues spring-projects-issues commented Mar 6, 2018

Juergen Hoeller opened SPR-16558 and commented

Spring's JDBC module provides several abstractions for provider-specific database mechanisms, in particular jdbc.support.incrementer. Over time, several inconsistencies have accumulated in the support for various databases there, in terms of class naming as well as database identification.

Let's use the 5.0.5 / 4.3.15 wrap-up (before entering the maintenance phase there) as an opportunity to revisit the support for PostgreSQL, DB2 (including its new LUW naming for the the Linux, Unix, Windows product) and SAP HANA ("HDB" as the primary JDBC database product name, and introducing a HanaSequenceMaxValueIncrementer).


Issue Links:

  • #21099 PostgresTableMetaDataProvider.isGetGeneratedKeysSimulated() does not detect Postgres 10
  • #21005 Add SAP HANA to common JPA database platforms
  • #18833 Add database product name for SAP HANA

Referenced from: commits 0962c66, 82515a3

Backported to: 4.3.15

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: data status: backported type: enhancement
Projects
None yet
Development

No branches or pull requests

2 participants