Why is Rails is adding `OR 1=0` to queries using the where clause hash syntax with a range?

Question

The project that I\'m working on is using MySQL on RDS (mysql2 gem specifically).

When I use a hash of conditions including a range in a where statement

Answer 1

This is strictly speaking a guess, since I did something similar in a project of my own (although I used AND 1).

For whatever reason, when generating a query, it is easier to always have a WHERE clause containing a no-op than it is to conditionally generate the WHERE clause at all. That is, if you don't include any where sections it will end up generating something still valid.

On the other hand, I'm not sure why it's taking this form: when I did it I use 1 [...] it allowed arbitrary chaining, but I don't see how what you're seeing would allow it. None the less, I still think it likely to be a result of an algorithmic code generation scheme.