OR support in /rows query parameter?

[Marcel_Darvas]

I am bumping this as I also was looking for a solution to this!

EDIT: It seems like this has not been built yet. The solution is to create a filtered view and call rows from there

Multiple query options when getting rows via API

Hi, I’m building a pythonic library for the coda API, and the querying limitations of the “list table rows” endpoint are a major pain point. Currently the only option for many manipulations is to list all rows and do the filtering on the client side, which becomes slow and expensive for large tables. Sometimes I can loop through the rows I need and request them one by one. But this is often slower than getting all the rows even if we are only requesting a dozen rows or so, due to so many roun…