rmannibucau opened a new pull request, #8787:
URL: https://github.com/apache/hop/pull/8787

   PR #8034 (Issue #2722) made Table Input read parameter rows from every 
incoming hop, even with an empty "Insert data from transform". Pipelines that 
feed a Table Input for sequencing only (e.g. a header transform before the 
extraction) now had their header row bound to the statement even though the SQL 
has no bind variable, failing on Oracle with ORA-17003 "Invalid column index" 
and on H2 with "Parameter index out of range".
   
   Fix both sides of the regression while keeping the 2.20 feature:
   
   - TableInputSql: count real positional placeholders (?) outside string 
literals, quoted identifiers, comments and Hop variables. prepare() with named 
parameters disabled and bind() now return a Bound with null parameter 
metadata/data when the SQL has no placeholder, so Database runs a plain 
statement instead of a PreparedStatement.
   - TableInput: in the assemble-all branch, when the lookup is empty and named 
parameters are disabled and the SQL has no placeholder, drain the incoming rows 
without collecting or binding them. Upstream transforms still complete 
(sequencing contract of 2.19) and consumesMainInput() stays true so the 
unconsumed-main-input check keeps passing.
   - Named and positional parameters are still read from every incoming hop 
(optional lookup, PR #8034) when the SQL declares them.
   
   Tests: new TableInputTest with an in-memory H2 connection reproduces the 
failure before the fix (openQuery receives the header row on "SELECT 1") and 
guards named/positional binding, literal '?' handling and the legacy 
drain-without-bind path. TableInputSqlTest updated accordingly. Documentation: 
tableinput.adoc now describes the no-placeholder behavior and the 2.19/2.20 
compatibility.
   
   ------------------------
   
   Thank you for your contribution! Follow this checklist to help us 
incorporate your contribution quickly and easily:
   - [ ] Run `mvn clean install apache-rat:check` to make sure basic checks 
pass. A more thorough check will be performed on your pull request 
automatically.
   - [X] If you have a group of commits related to the same change, please 
squash your commits into one and force push your branch using `git rebase -i`.
   - [-] Mention the appropriate issue in your description (for example: 
`addresses #123`), if applicable.
   
   To make clear that you license your contribution under the [Apache License 
Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
   you have to acknowledge this by using the following check-box.
   
   - [X] I hereby declare this contribution to be licensed under the [Apache 
License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
   - [X] In any other case, please file an [Apache Individual Contributor 
License Agreement](https://www.apache.org/licenses/icla.pdf).
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to