table: fix shared query filtering

[IndAlok]

Your checklist for this pull request

• I've read the guidelines for contributing to this repository.
• I made sure to follow the project's coding style.
• I've documented every RZ_API function and struct this PR changes.
• I've added tests that prove my changes are effective (required for changes to RZ_API).
• I've updated the Rizin book with the relevant information (if needed).
• I've used AI tools to generate fully or partially these code changes and I'm sure the changes are not copyrighted by somebody else.

Detailed description

This PR fixes a table filtering issue that was reported while testing table query syntax on binaries. (as described in rizinorg/book#159, i used curl-example-dbg from testbins for reproducibility and testing)

The issue is the shared table query/filter engine behind commands like izz, is and other table cmds. This caused cmds such as:

izz:string/minlen/8:length/sort/rev:*/page/0/15:csv

to emit rz_num_calc errors on ordinary str contents, and cmds such as:

is:name/uniq:addr/gt/0x1000:name/str/init:addr/sort:json

to behave incorrectly when the query used common names like addr or length that do not always exactly match the underlying table headers.

The changes do three things:

1. They make num parsing lazy in rz_table_query() / table_filter().
   Before this change, row values were eagerly sent to rz_num_math() even for str-only operations such as str, minlen, and maxlen. That is what produced the rz_num_calc errors.
   After this change, num parsing only happens for operators that actually require num semantics.

2. They make string eq/ineq stay str based on str columns.
   This avoids accidental numeric treatment of values such as "16", "010", and "0x10" when the column itself is txt.

3. They add query time column resolution for stable aliases such as addr -> vaddr/address/paddr and length -> len, while preserving the existing cols behavior expected by older query chains.

Tests were also added:

• new unit coverage was added for the shared table query regressions
• db tests were added for the izz string/minlen case and the is addr-alias case
• the addr-alias db test was made deterministic by sorting by name after filtering by addr, so it doesn't depend on platform specific ordering of eq-addr rows

Test plan

Before:

After:

Closing issues

closes #5993

[codecov]

Codecov Report

❌ Patch coverage is 45.10870% with 101 lines in your changes missing coverage. Please review.
✅ Project coverage is 48.24%. Comparing base (b11bb9d) to head (9325f01).
⚠️ Report is 1 commits behind head on dev.

Files with missing lines	Patch %	Lines
librz/util/table.c	45.10%	61 Missing and 40 partials ⚠️

Additional details and impacted files

Files with missing lines	Coverage Δ
librz/util/table.c	63.71% <45.10%> (-3.04%)	⬇️

... and 11 files with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b11bb9d...9325f01. Read the comment docs.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[wargio]

split this into 2 PRs. one for windows console and one for the table query

[IndAlok]

split this into 2 PRs. one for windows console and one for the table query

Detailed description (PR)

This PR fixes two separate problems (however testing one lead to identification of another, hence could be considered ig)

I thought in this case, could be considered. Np, will split.

[wargio]

split this into 2 PRs. one for windows console and one for the table query

Detailed description (PR)

This PR fixes two separate problems (however testing one lead to identification of another, hence could be considered ig)

I thought in this case, could be considered. Np, will split.

i think you should fix first only the table, then we can fix the terminal

[wargio]

i think you should check the type. usually when you define a row you use xxssXsu etc.. to define if is a number or a string.

[IndAlok]

yep, now table_column_is_numeric() treats NUMBER and BOOL cols as num comaptible, table_query_index_of_numeric_column() resolves header name first & rejects it unless the target col is num, & in table_query_index_of_column(), the addr and length alias fallback goes through the num only helper...
have used ex2 and 3 from book for test as well

[wargio]

it's a quite nice improvement.

Please test the book queries: https://book.rizin.re/src/tools/rz-bin/tables.html

[IndAlok]

it's a quite nice improvement.

Please test the book queries: https://book.rizin.re/src/tools/rz-bin/tables.html

ex 2 and 3 seem to be successfull (#6166 (comment)), however, for ex1, this is the quote from book:
Note: Table specifiers are applied from left to right. Output format specifiers must be specified at the end.

and this is the ex1 provided,
aflt:addr/cols/name/nbbs:size/gt/32:nbbs/gt/1:nbbs/lt/10:nbbs/sort/rev:fancy

addr/cols/name/nbbs is handled by table_query_select_columns(), which turns that into a selected col list and then calls rz_table_columns_select(), and table has 3 cols left only: addr, name & nbbs. then size/gt/32 is there, but size no longer exists in the table, because cols already removed it, and hence we get ERROR: table: Invalid column (size).

however, aflt:size/gt/32:nbbs/gt/1:nbbs/lt/10:addr/cols/name/nbbs:nbbs/sort/rev:fancy would work as size & nbbs is still present when it is filtered and sorted, and after that we reduce the cols...