Fixes the issue introduced by commit rails/rails@a1c05dd and discussed in issue rails/arel#133.
It's not the ideal solution, but it's only three lines and seems to do the trick.
(And yes, there are apps that use both Sequel and ActiveRecord.)
Fix incompatibility between Sequel and Arel in Rails 3.2.8.
Added test for Sequel/Arel compatibility fix.
I'm -1 on this. I offered that solution as something that Sequel could patch in via a compatibility fix, but otherwise, this discussion (and any fix) should remain on AR, where the node gets created, not ARel, IMHO.
I guess this should be closed