aboutsummaryrefslogtreecommitdiffstats
path: root/activerecord/test/cases/custom_locking_test.rb
diff options
context:
space:
mode:
authorYves Senn <yves.senn@gmail.com>2014-01-22 14:20:01 +0100
committerYves Senn <yves.senn@gmail.com>2014-02-23 12:47:30 +0100
commit91949e48cf41af9f3e4ffba3e5eecf9b0a08bfc3 (patch)
tree38baccfd5b5275cbb2636bee15da82691dd6d521 /activerecord/test/cases/custom_locking_test.rb
parent4cb47167e747e8f9dc12b0ddaf82bdb68c03e032 (diff)
downloadrails-91949e48cf41af9f3e4ffba3e5eecf9b0a08bfc3.tar.gz
rails-91949e48cf41af9f3e4ffba3e5eecf9b0a08bfc3.tar.bz2
rails-91949e48cf41af9f3e4ffba3e5eecf9b0a08bfc3.zip
deprecate support for pg ranges with excluding beginnings.
The Ruby Range object does not support excluding beginnings. We currently support excluding beginnings for some subtypes using manually by incrementing them (now using the `#succ` method). This is approach is flawed as it's not equal to an excluding beginning. This commit deprecates the current support for excluding beginnings. It also raises an `ArgumentError` for subtypes that do not implement the `succ` method. This is a temporary solution to get rid of the broken state. We might still add complete support for excluding beginnings afterwards. (Probably with a new `PGRange` object, which acts like a `Range` but has excluding beginnings.
Diffstat (limited to 'activerecord/test/cases/custom_locking_test.rb')
0 files changed, 0 insertions, 0 deletions