Skip to content

Add DataFieldMaxValueIncrementer for MariaDB #29306

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

Closed
fmbenhassine opened this issue Oct 12, 2022 · 1 comment
Closed

Add DataFieldMaxValueIncrementer for MariaDB #29306

fmbenhassine opened this issue Oct 12, 2022 · 1 comment
Assignees
Labels
in: data Issues in data modules (jdbc, orm, oxm, tx) status: superseded An issue that has been superseded by another type: enhancement A general enhancement

Comments

@fmbenhassine
Copy link
Contributor

Spring Framework started treating MariaDB as an independent database here: #28355. However, it does not provide a dedicated DataFieldMaxValueIncrementer for it.

To give a bit of context, we have the same request in Spring Batch (to treat MariaDB as independent database, see spring-projects/spring-batch#3891), but due to the lack of a dedicated incrementer, we would have to use the MySQL one, which feels odd given the intent in the first place. Do you agree?

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged or decided on label Oct 12, 2022
@sbrannen sbrannen added in: data Issues in data modules (jdbc, orm, oxm, tx) type: enhancement A general enhancement labels Oct 13, 2022
@sbrannen sbrannen added this to the Triage Queue milestone Oct 13, 2022
@jhoeller jhoeller removed the status: waiting-for-triage An issue we've not yet triaged or decided on label Oct 24, 2022
@jhoeller jhoeller self-assigned this Oct 24, 2022
@jhoeller jhoeller modified the milestones: Triage Queue, 6.0.0-RC3 Oct 24, 2022
fmbenhassine added a commit to fmbenhassine/spring-framework that referenced this issue Oct 25, 2022
@jhoeller jhoeller added the status: superseded An issue that has been superseded by another label Oct 25, 2022
@jhoeller
Copy link
Contributor

Superseded by PR #29379.

@jhoeller jhoeller removed this from the 6.0.0-RC3 milestone Oct 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: data Issues in data modules (jdbc, orm, oxm, tx) status: superseded An issue that has been superseded by another type: enhancement A general enhancement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants