Does DataGrip's toolbar Limit control adapt to dialects like SQL Server and Oracle?

Bounding a large result set across mixed dialects

DataGrip separates two concerns when working with big result sets. The fetch size (Result set page size, 500 rows by default) controls how many rows are pulled per round-trip while scrolling, and the Limit input in the query console toolbar appends a LIMIT clause to the executed statement. The data editor can page through the grid, but only over rows that were already fetched.

The open issue is dialect awareness. Bare LIMIT is valid in PostgreSQL and MySQL, but SQL Server expects TOP n and Oracle 12c+ expects FETCH FIRST n ROWS ONLY. Newer releases (2023.3 and later) also added a pagination option to the export dialog that depends on OFFSET/LIMIT-style syntax, so the same portability question applies there.

Before standardizing on the toolbar control for a workspace that mixes database engines, the behavior to confirm is:

• Does the Limit input generate dialect-specific SQL (TOP, FETCH FIRST), or does it always append literal LIMIT syntax?
• When the appended clause is unsupported by the dialect, is writing pagination manually in the statement the intended workflow?
• Does export pagination skip or fail on databases without OFFSET/LIMIT support?