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

Update DerbyPagingQueryProvider for Derby 10.7 and above #1673

Closed
spring-projects-issues opened this issue Dec 10, 2012 · 2 comments
Closed

Comments

@spring-projects-issues
Copy link
Collaborator

Mikalai Dushkou opened BATCH-1921 and commented

Since Derby DB from version 10.7 support "OFFSET" and "FETCH FIRST"/"FETCH NEXT" clauses it nice to have this option. Please see implemented solution in attached file.


Attachments:

@spring-projects-issues
Copy link
Collaborator Author

Mahmoud Ben Hassine commented

@Mikalai Dushkou Can you please open a PR on Github with the attached file? Please make sure to test it against the latest derby version supported by Spring Batch which is 10.14.2.0 ( and not v10.7 since this issue was created in 2012).

Thank you in advance!

@spring-projects-issues spring-projects-issues added status: waiting-for-triage Issues that we did not analyse yet type: enhancement status: waiting-for-reporter Issues for which we are waiting for feedback from the reporter in: infrastructure labels Dec 16, 2019
@fmbenhassine fmbenhassine removed status: waiting-for-triage Issues that we did not analyse yet status: waiting-for-reporter Issues for which we are waiting for feedback from the reporter labels Dec 6, 2024
@fmbenhassine fmbenhassine added this to the 5.2.1 milestone Dec 6, 2024
@fmbenhassine fmbenhassine changed the title DerbyPagingQueryProvider for Derby 10.7 and above [BATCH-1921] Update DerbyPagingQueryProvider for Derby 10.7 and above Dec 6, 2024
@fmbenhassine
Copy link
Contributor

Resolved with #4713 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants