Repository navigation
fix: enforce bounded SELECT results - #33
Merged
Merged
Conversation
Owner
Author
|
Final post-green audit complete on head
|
marianfoo
marked this pull request as ready for review
August 7, 2026 16:14
This was referenced Aug 7, 2026
marianfoo
pushed a commit
that referenced
this pull request
Aug 7, 2026
🤖 I have created a release *beep* *boop* --- ## [5.0.1](5.0.0...5.0.1) (2026-08-07) ### Bug Fixes * bound temporary subroutine pools ([#32](#32)) ([ef54657](ef54657)) * classify ZTOAD table as not extensible ([#26](#26)) ([e5ae759](e5ae759)) * enforce bounded SELECT results ([#33](#33)) ([b6acc14](b6acc14)) * execute queries safely in WebGUI ([#24](#24)) ([5218476](5218476)) * execute UNION as one SQL set ([a5ad27c](a5ad27c)) * generate aggregate CASE result types ([#21](#21)) ([d532b2e](d532b2e)) * isolate generated query failures ([#31](#31)) ([b0b4d9f](b0b4d9f)) * parse top-level SQL clauses ([#28](#28)) ([c5ca65b](c5ca65b)) * support ABAP SQL string functions ([#27](#27)) ([0f056e8](0f056e8)) * verify complete native-abapGit installation ([#22](#22)) ([2360fe4](2360fe4)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Root cause
ABAP treats a zero UP TO value as up to 2,147,483,647 rows on the supported releases. ZTOAD stripped the clause and reused initial
fw_rowsas an “omit the cap” sentinel in every generated SELECT path. A saved default of zero reached the same bypass.TDD evidence
ccea897on NPL: 113 tests, 112 passed; onlyLTC_QUERY_PARSER->REJECTS_ZERO_LIMITfailed832d057656dc2923e79b87eff5016b718dad42feb8d5d7807e42832b105deabe4d55f142ee10408a4f1ef975cf9530d17cf2ebb4Validation
npm ci,npm test, configured abaplint zero findings, repository/installation contracts, andgit diff --checkpassedUP TO 0 ROWSwas rejected before execution; a positive two-row limit returned exactly two rows; no new ST22 dumpmasterand verified at 113/113 tests with zero inactive ZTOAD partsThe S/4HANA readiness variant showed zero displayed findings, but remains recorded as incomplete because prerequisite execution could not be proven.
Tracking: BASE-RUN-004.