diff options
author | Sean Griffin <sean@seantheprogrammer.com> | 2016-05-06 11:55:21 -0500 |
---|---|---|
committer | Sean Griffin <sean@seantheprogrammer.com> | 2016-05-06 11:58:01 -0500 |
commit | 96f3f3d8267167d5d4c5697f2299756cfa7e37d4 (patch) | |
tree | 4159b2de70d916cb85d420906d4a2acf6b414950 /activerecord/lib/active_record/connection_adapters/sqlite3 | |
parent | c763c00b5e7cdfc7e5523502f7be77314cbfff7b (diff) | |
download | rails-96f3f3d8267167d5d4c5697f2299756cfa7e37d4.tar.gz rails-96f3f3d8267167d5d4c5697f2299756cfa7e37d4.tar.bz2 rails-96f3f3d8267167d5d4c5697f2299756cfa7e37d4.zip |
Allow the connection adapters to determine the order of bind params
In 5.0 we use bind parameters for limit and offset, while in 4.2 we used
the values directly. The code as it was written assumed that limit and
offset worked as `LIMIT ? OFFSET ?`. Both Oracle and SQL Server have a
different syntax, where the offset is stated before the limit. We
delegate this behavior to the connection adapter so that these adapters
are able to determine how the bind parameters are flattened based on
what order their specification has the various clauses appear.
Fixes #24775
Diffstat (limited to 'activerecord/lib/active_record/connection_adapters/sqlite3')
0 files changed, 0 insertions, 0 deletions