Skip to content

fix(task) #30 DatabaseReaderTask no longer drops rows with the paginate option - #31

Merged
njoubert-cleverage merged 1 commit into
mainfrom
30
Sep 30, 2026
Merged

njoubert-cleverage merged 1 commit into
mainfrom
30

Conversation

@njoubert-cleverage

Copy link
Copy Markdown
Member

Description

Fixes #30.

With the paginate option, DatabaseReaderTask fetched one row beyond each full page and never output it. The pagination loop now stops fetching as soon as the page is full, so every row is output exactly once.

  • DatabaseReaderTask::execute(): the page starts with the current row, and rows are fetched only while the page is not full
  • DatabaseReaderTaskTest::testExecuteWithPaginationDoesNotLoseRows: 3 rows read by pages of 2 give [row1, row2] then [row3] (fails without the fix)
  • database_reader_task.md: remove the note about the lost rows

Checked with demo.doctrine.database.read_paginate in process-bundle-demo (3 books, pages of 2): "89,90" then "91" (only "89,90" before).

Requirements

  • Documentation updates
    • Reference
    • Changelog
  • Unit tests

Breaking changes

None.

🤖 Generated with Claude Code

…ch full page with the paginate option

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@njoubert-cleverage njoubert-cleverage added the bug Something isn't working label Sep 30, 2026
@njoubert-cleverage njoubert-cleverage self-assigned this Sep 30, 2026
@njoubert-cleverage njoubert-cleverage added the bug Something isn't working label Sep 30, 2026
@njoubert-cleverage
njoubert-cleverage merged commit a6edaad into main Sep 30, 2026
22 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

DatabaseReaderTask drops one row after every full page with the paginate option

1 participant