Bug: NocoDB node's "Get Many" does not respect limit below 10

[miteshashar]

Bug Description

The NocoDB node's "Get Many" operation has an option to limit the number of rows fetched.

If I set it to anything below 10, it does not respect the value and returns 10 rows.

In tables that have many columns(and I need all/most of them) or contain binary files, that tends to make the workflow memory consumption high. That is not desirable, specially when I am fine with loading lesser number of rows.

Just for reference, I already checked #2866 & #3022. They are different.

To Reproduce

1. Add a NocoDB node with action "Get many rows".
2. Select the requisite options with "Limit" set as any number below 10.
3. Test the node.
4. There are 10 rows returned in output.

Expected behavior

The node should return rows equivalent to the set limit.

Operating System

Ubuntu Server 24.04.1 LTS

n8n Version

1.72.1

Node.js Version

20.18.0

Database

PostgreSQL

Execution mode

queue

[Joffcom]

Hey @miteshashar,

We have created an internal ticket to look into this which we will be tracking as "N8N-7998"