Feature Request: Implement Pagination in Data Viewer for Improved Performance #8
Description
Currently, when viewing data from a table (right-click -> "Data"), the extension appears to fetch all rows from the table at once. This leads to significant performance degradation, high memory consumption, and a long wait time when working with tables containing a large number of rows (e.g., tens of thousands or more).
This behavior makes it impractical to quickly inspect data in large production tables, which is a very common task.
Steps to Reproduce
Connect to an Oracle database using the SQL Developer extension.
In the "ORACLE EXPLORER" panel, locate a table with a substantial number of rows (e.g., > 50,000 rows).
Right-click on the table name and select "Data".
Observe the loading indicator as the extension attempts to fetch the entire result set, which can take a very long time or cause the UI to become unresponsive.
Expected Behavior
The data grid should load almost instantly by fetching only the first "page" of data (e.g., the first 50 or 100 rows).
The data viewer UI should then provide pagination controls (like "Next >", "< Previous", and a page number input) to allow the user to navigate through the rest of the data page by page. This is standard behavior in most database clients, including the standalone SQL Developer desktop application.
Suggested Solution
The data fetching logic could be modified to use Oracle's OFFSET FETCH clause for efficient, server-side pagination.
For example, to fetch the first page of 50 rows