René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[Order 04][P1] Fix Oracle CommitStampStart recursion after Oracle tests are enabled","articleBody":"## Priority order\n\nOrder: 04 of 09\nPriority: P1 correctness\nBlocked by: #58\n\n## Problem\n\n`OracleNativeDialect.CommitStampStart` recursively calls itself.\n\nEvidence:\n\n- `src/NEventStore.Persistence.Sql/SqlDialects/OracleNativeDialect.cs:55`\n- Getter calls `MakeOracleParameter(CommitStampStart)` instead of `MakeOracleParameter(base.CommitStampStart)`.\n\n## Impact\n\nOracle date-range reads that need `CommitStampStart` can stack overflow before executing SQL.\n\n## Mandatory test-first workflow\n\n- Complete #58 first or explicitly document why Oracle tests still cannot run.\n- Add tests before changing production code.\n- At minimum, add a unit test against `new OracleNativeDialect().CommitStampStart`.\n- Add or enable Oracle integration coverage for `GetFromTo(bucketId, startDate, endDate)` once Oracle tests can run.\n\n## Proposed action\n\n- Change the getter to `MakeOracleParameter(base.CommitStampStart)`.\n\n## Acceptance criteria\n\n- Oracle `CommitStampStart` returns `:CommitStampStart` without recursion.\n- Oracle date-range read tests pass when Oracle test infrastructure is available.\n- No Oracle production-code fix is merged before the test prerequisite is addressed.\n\nSource: `docs/Project-Analysis-Issue-Drafts.md`.","author":{"url":"https://github.com/AGiorgetti","@type":"Person","name":"AGiorgetti"},"datePublished":"2026-06-11T09:20:57.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/61/NEventStore.Persistence.SQL/issues/61"}