Why does AREL add OR IN (NULL) to BETWEEN terms?

Question

Why does AREL add OR IN (NULL) to BETWEEN terms?

The model has a scope:

scope :daily, lambda {|day| where :post_time => 
  [day.beginning_of_day() .. day.end_of_day()] }

:post_time

declares non-nullable on the database, but AREL insists on adding false IN (NULL)

to the generated SQL:

SELECT `<table>`.* FROM `<table>` 
WHERE (`<table>`.`post_time` 
     BETWEEN '2013-02-05 00:00:00' AND '2013-02-05 23:59:59' 
     OR `<table>`.`post_time` IN (NULL))

How can I stop it from doing this? Obviously I can add another condition not_eq(nil)

, :post_time != nil

or similar, but my question is why AREL does this, and how can I prevent it without additional conditions to negate it.

+3

ruby activerecord ruby-on-rails-3 arel

Remus Rusanu 12 Feb 13 at 11:23

source to share

1 answer

Frederick cheung · Accepted Answer · 2013-02-12T13:19:36+0000

It looks like you are confusing isl by passing in an array of ranges (although why this adds an extra clause I'm not sure).

scope :daily, lambda {|day| where :post_time => 
  (day.beginning_of_day() .. day.end_of_day()) }

should be fine.

Why does AREL add OR IN (NULL) to BETWEEN terms?

More articles: