On Saturday, November 9, 2013 3:18:13 AM UTC-8, Robert Payne wrote: > I was curious to check and see if there is a reason Sequel.or is different > than Sequel.| > > Sequel.or seems extremely limited in functionality to two condition hashes > where as Sequel.| can take more complex things like a Sequel.& or a > Sequel.~. > > I was just curious if there is a good reason behind this -- I'm just a > novice here took me a little while to dig in to find out I had to use > Sequel.| instead of Sequel.or >
Sequel.or is the replacement for Array#sql_or and Hash#sql_or in the core_extensions. It's designed for taking a single array or hash and treating the internal conditions it contains with OR instead of AND (the default). Sequel.| is the replacement for the | operator in the core extensions. It's designed to take an arbitrary number of expressions and combining them with OR. Thanks, Jeremy -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sequel-talk. For more options, visit https://groups.google.com/groups/opt_out.
