mirror of
https://github.com/rails/rails.git
synced 2022-11-09 12:12:34 -05:00
6e638bba59
People are often trying to use ARel nodes inside ActiveRecord, and when they do so, lots of things can break, because ActiveRecord relies on Array#uniq and sometimes hash key equality to handle values that end up in wheres, havings, etc. By implementing equality for all the nodes, we should hopefully be able to prevent any nodes (even nodes containing other nodes) from failing an equality check they should otherwise pass, and alleviate many of these errors. Fixes #130
49 lines
1.4 KiB
Ruby
49 lines
1.4 KiB
Ruby
require 'helper'
|
|
|
|
describe Arel::Nodes::SelectStatement do
|
|
describe "#clone" do
|
|
it "clones cores" do
|
|
statement = Arel::Nodes::SelectStatement.new %w[a b c]
|
|
|
|
dolly = statement.clone
|
|
dolly.cores.must_equal statement.cores
|
|
dolly.cores.wont_be_same_as statement.cores
|
|
end
|
|
end
|
|
|
|
describe 'equality' do
|
|
it 'is equal with equal ivars' do
|
|
statement1 = Arel::Nodes::SelectStatement.new %w[a b c]
|
|
statement1.offset = 1
|
|
statement1.limit = 2
|
|
statement1.lock = false
|
|
statement1.orders = %w[x y z]
|
|
statement1.with = 'zomg'
|
|
statement2 = Arel::Nodes::SelectStatement.new %w[a b c]
|
|
statement2.offset = 1
|
|
statement2.limit = 2
|
|
statement2.lock = false
|
|
statement2.orders = %w[x y z]
|
|
statement2.with = 'zomg'
|
|
array = [statement1, statement2]
|
|
assert_equal 1, array.uniq.size
|
|
end
|
|
|
|
it 'is not equal with different ivars' do
|
|
statement1 = Arel::Nodes::SelectStatement.new %w[a b c]
|
|
statement1.offset = 1
|
|
statement1.limit = 2
|
|
statement1.lock = false
|
|
statement1.orders = %w[x y z]
|
|
statement1.with = 'zomg'
|
|
statement2 = Arel::Nodes::SelectStatement.new %w[a b c]
|
|
statement2.offset = 1
|
|
statement2.limit = 2
|
|
statement2.lock = false
|
|
statement2.orders = %w[x y z]
|
|
statement2.with = 'wth'
|
|
array = [statement1, statement2]
|
|
assert_equal 2, array.uniq.size
|
|
end
|
|
end
|
|
end
|