Hibernate Pagination Integration: setFirstResult/setMaxResults with Dialect‑Specific LIMIT/OFFSET and FETCH FIRST/OFFSET

Goal: Verify that Hibernate’s setFirstResult and setMaxResults produce identical offset‑based pagination across PostgreSQL, MySQL, Oracle, and SQL Server when the query includes a non‑unique ORDER BY clause.

Uncertainty: Different Hibernate releases may translate the same API call into dialect‑specific SQL differently, and some versions switch to in‑memory pagination when the join cardinality creates a Cartesian product, which can affect performance and result consistency.

Questions: Does Hibernate 6.2 generate the same LIMIT/OFFSET clause for PostgreSQL and MySQL as it does FETCH FIRST/OFFSET for Oracle and SQL Server under these conditions? Is there a version threshold where in‑memory pagination is avoided for non‑unique ORDER BY? How can the generated SQL be inspected to confirm dialect alignment without executing the query?