#13: RED bounded duplicate-aware secondary-index range #13
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nsaspy/tek9!13
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "rage/13-index-range-duplicates-red"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
RED-first generic Tek9 dependency for
lost-rob0t/llm-log#15.The new index test requires
select-index-rangeto enumerate all DUPSORT postings for the same secondary key while respecting:limitand inclusive range bounds.index-fetchalready proves duplicates are stored, but it is unbounded; the expert-plane dataset query needs the existing bounded public primitive to be duplicate-aware.No production mutation in this initial PR head. Expected master failure: exact-key range over two
apostings returns fewer than both.Adversarial review found this RED premise was wrong.
lmdb:cursor-nexton a DUPSORT database advances through duplicate values, and Tek9's currentselect-index-rangeuses that operation correctly. The llm-log fixture's second supposedsuccessused authoritativeuser_feedback=success, which the current SWI-Prolog outcome contract deliberately maps tounknownrather than success. That left only one success assertion, sotruncated=falsewas correct. No Tek9 production change is justified; closing this draft without merge.View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.