You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Status: completed locally on 2026-06-11. GitHub issue update is pending review.
285
+
Status: completed on 2026-06-11.
286
286
287
287
Async paged reads now complete when the configured page size is `0`. For pageable dialects, `ExecutePagedQueryAsync` still binds the SQL limit parameter with an effectively unbounded value, but keeps the local paging size at `0` so continuation does not request another page.
Status: completed on 2026-06-11. GitHub issue updated in comment `4681420070`.
310
+
311
+
Oracle date-range reads no longer recurse while binding `CommitStampStart`. `OracleNativeDialect.CommitStampStart` now wraps `base.CommitStampStart`, matching the other Oracle parameter overrides. The Oracle dialect also now provides an Oracle-native `GetCommitsFromToInstant` statement, because the new integration coverage showed that after the recursion was fixed, Oracle was still falling back to the common `LIMIT/OFFSET` date-range SQL.
312
+
313
+
Implementation notes:
314
+
315
+
- Added Oracle regression coverage under `src/NEventStore.Persistence.Oracle.Tests/OracleCommitStampStartTests.cs`.
316
+
- The direct dialect test verifies `new OracleNativeDialect().CommitStampStart` returns `:CommitStampStart`.
317
+
- The Oracle integration test commits two events in one bucket and verifies `GetFromTo(bucketId, startDate, endDate)` returns only the commit inside the requested timestamp range.
318
+
- The production fix is scoped to Oracle dialect parameter and date-range SQL behavior.
319
+
320
+
Validation:
321
+
322
+
- Test-first check: the new Oracle date-range regression crashed the test host before the fix with a stack overflow in `OracleNativeDialect.get_CommitStampStart`.
323
+
- After the getter fix, the same regression exposed Oracle fallback to common `LIMIT/OFFSET` date-range SQL; adding the Oracle-native date-range statement fixed that provider issue.
324
+
-`dotnet test .\src\NEventStore.Persistence.Oracle.Tests\NEventStore.Persistence.Oracle.Core.Tests.csproj -c Release -f net8.0 --no-build --filter "FullyQualifiedName~when_getting_the_oracle_commit_stamp_start_parameter"`
325
+
- Result: 1 passed, 0 failed, 0 skipped.
326
+
-`dotnet test .\src\NEventStore.Persistence.Oracle.Tests\NEventStore.Persistence.Oracle.Core.Tests.csproj -c Release -f net8.0 --no-restore --filter "FullyQualifiedName~CommitStampStart|FullyQualifiedName~when_reading_oracle_commits_between_commit_stamps"`
327
+
- Result: 2 passed, 0 failed, 0 skipped.
328
+
-`dotnet test .\src\NEventStore.Persistence.Oracle.Tests\NEventStore.Persistence.Oracle.Core.Tests.csproj -c Release -f net8.0 --no-build`
0 commit comments