Read more

Don't compare datetimes with date ranges in MySQL and PostgreSQL

Henning Koch
January 04, 2012Software engineer at makandra GmbH

When selecting records in a date range, take care not to do it like this:

start_date = Date.parse('2007-05-01')
end_date = Date.parse('2007-05-31')
LogItem.where(:created_at => start_date .. end_date)
Illustration UI/UX Design

UI/UX Design by makandra brand

We make sure that your target audience has the best possible experience with your digital product. You get:

  • Design tailored to your audience
  • Proven processes customized to your needs
  • An expert team of experienced designers
Read more Show archive.org snapshot

The problem is that created_at is a datetime (or Time in Ruby), while start_date and end_date are simple dates. In order to make sense of your query, your database will cast your dates to datetimes where the time component is 00:00:00. Because of this the query above will lose records created from 2007-05-31 00:00:01 to 2007-05-31 23:59:59.

Details

The Ruby code above triggers the following query:

SELECT * FROM log_items WHERE created_at BETWEEN '2007-05-01' AND '2007-05-31'

Your database sees that you are trying to compare a datetime with a date and silently casts your query to:

SELECT * FROM log_items WHERE created_at BETWEEN '2007-05-01 00:00:00' AND '2007-05-31 00:00:00'

Note how you just lost all records from 2007-05-31 00:00:01 to 2007-05-31 23:59:59.

Solutions

One solution is to cast the datetime to a date before you make the query:

LogItem.where('DATE(log_items.created_at) BETWEEN ? AND ?', start_date, end_date)

This may cause an index on the column to no longer be used.

Another solution is to be more explicit about what you want to select:

LogItem.where(:created_at => start_date.beginning_of_day..end_date.end_of_day)
Posted by Henning Koch to makandra dev (2012-01-04 13:45)