But seems a bit strange to search a value that query already tried to get?
If you want to use directly ${q_result} (do the query then check content) , you could use Evaluate:
${hasValue} Evaluate "D80" in ${q_result}
This is a quick example, you will probably have to managed multilines results/lists and loop over uncompressed tuples to manage all cases and q_result format.
Wouldn’t just simple count do in this case ? If the original SQL query has WHERE c_prot = 'D80' then the query wont return any rows if c_prot is not D80 and thus it is quaranteed to have that value on each row returned by the query ?
Yeah totally, that’s why I mention the Select that already search for D80.
A count is a fast solution to know if present, and will return occurrences as a bonus.
Nice!
I put D80 in “where and search” for the example, Sorry it’s stupide
I filter with D80 and I can have one or more rows.
Then, I search for values without specifying the columns, just to quickly check if my values are up to date.
I could count the columns and rows and then loop, but I’m looking for a simple and quick solution.
Thanks again.