diff options
| author | Mike Bayer <mike_mp@zzzcomputing.com> | 2022-07-07 12:07:39 -0400 |
|---|---|---|
| committer | Mike Bayer <mike_mp@zzzcomputing.com> | 2022-07-20 11:02:24 -0400 |
| commit | 5fc46b192b5005fa6962110a683abf1d296786d8 (patch) | |
| tree | e0988fe61c6d4b79c71dc84b265885a13df6f74f /test/dialect/postgresql/test_reflection.py | |
| parent | d5e31d130808c94f09e51e9afb222c4efa63875c (diff) | |
| download | sqlalchemy-5fc46b192b5005fa6962110a683abf1d296786d8.tar.gz | |
Use FETCH FIRST N ROWS / OFFSET for Oracle LIMIT/OFFSET
Oracle will now use FETCH FIRST N ROWS / OFFSET syntax for limit/offset
support by default for Oracle 12c and above. This syntax was already
available when :meth:`_sql.Select.fetch` were used directly, it's now
implied for :meth:`_sql.Select.limit` and :meth:`_sql.Select.offset` as
well.
I'm currently setting this up so that the new syntax renders
in Oracle using POSTCOMPILE binds. I really have no indication
if Oracle's SQL optimizer would be better with params
here, so that it can cache the SQL plan, or if it expects
hardcoded numbers for these. Since we had reports that the previous
ROWNUM thing really needed hardcoded ints, let's guess
for now that hardcoded ints would be preferable. it can be turned
off with a single boolean if users report that they'd prefer
real bound values.
Fixes: #8221
Change-Id: I812ec24ffc947199866947b666d6ec6e6a690f22
Diffstat (limited to 'test/dialect/postgresql/test_reflection.py')
0 files changed, 0 insertions, 0 deletions