[Feat]: Page Size Change for a query

[manojvignesh]

Prerequisites

• I have written a descriptive issue title
• I have searched existing issues to ensure the feature has not already been requested

🚀 Feature Proposal

Feature to change the Page Size for a query.
This is not the default page size change.

Motivation

Helpful to copy all the column values for all the pages instead of just the active page.

Example

No response

[debba]

If I understand correctly, your main goal is to copy the values of a column across the entire result set.

We already have “Copy All”, which fetches and copies all rows, including those outside the current page. However, “Copy column values” currently only copies values from the loaded page, and the page size can only be changed globally in Settings.

Would a “Copy column values from all rows” option solve your use case, or do you specifically need to change the page size for each query result?

[manojvignesh]

Copy column values from all rows

This will solve my problem.
I actually use Copy column values as SQL IN more often. So I'd need Copy column values as SQL IN from all rows.

I'm fine if both are added or if it felt like lot of options then we can add only the page size for a particular query result.

Also Just a thought:
If I can select a column somehow then I'm fine to access these advanced options through command palette.

[debba]

@manojvignesh I agree. We could add an export option using the same format as “Copy column values as SQL IN”, alongside CSV, JSON, and Markdown in the Export menu.

@verbaux It could also be useful to add these actions to the Command Palette in a follow-up PR, with options for both the current selection and all rows.

[manojvignesh]

@debba Export is something I consider to be a file export instead of copy. Though we can add copy or file as an option, it also work full table and not for a single column.

There is a way to select row/rows but nothing for columns which can be considered for export.

[debba]

@manojvignesh In that case, I am not totally sure of what you would like.
Would you like to create A PR? Maybe it's the quickest way and we can discuss directly on it.

[manojvignesh]

@debba I think a simple fix could be is to edit the page size.

[debba]

@manojvignesh By “page size,” do you mean the page size used for automatic pagination?

This determines how many rows are fetched and displayed on each page. It is not a separate setting—you can customize it under Settings → General → Data Editor → Result Page Size (Limit).

When a query returns more rows than the configured page size, the result is marked Auto paginated, and the remaining rows can be accessed using the pagination controls.

The configured page size for the editor is already present:

[manojvignesh]

The configured page size for the editor is already present:

While it takes the default value from "Result Page Size (Limit)" changing it doesn't override the Result Page Size (Limit).
The editor page size will always take the global value and add more pages.

When my global value is 50, and If I change the limit to 51, It'll add 2 pages instead of showing all 51 in one page.

[debba]

@manojvignesh you're right, the editor limit only caps the total number of rows, while the page size always comes from the global setting. That's why 51 rows with a global value of 50 end up on 2 pages.

I've opened #675 to address this: the pagination bar now has a rows-per-page selector that overrides the global "Result Page Size (Limit)" for that tab only. In your example you can set it to 51 (or "All") and get everything on a single page. The value is also persisted with the tab across restarts.

[manojvignesh]

Thanks.

This works.