Rider 2024.3 Data Grid Pagination with LIMIT/OFFSET Ignoring Fetch Size

Determine whether Rider 2024.3’s configurable fetch size limits the number of rows transferred when a SQL query already contains LIMIT/OFFSET clauses, particularly for MySQL 8 and MariaDB JDBC drivers that may prefetch rows.

The documentation states that fetch size controls rows per network round‑trip, but observations show the setting can be ignored when the driver reports client‑side cursor support, causing the driver to fetch additional rows beyond the fetch size before applying the LIMIT/OFFSET, which generates extra traffic and IDE memory usage.

Does Rider honor the fetch size for bounded queries on MySQL 8/MariaDB drivers? If not, what connection or driver settings can enforce row‑level fetching? Is there a way to prevent excess prefetching without removing the LIMIT/OFFSET clause?