Answer to this is "database specific and depending if there is an index on the column or not and how that index is organized",
some database-storage engine-index type combinations will opt a full table table scan instead of index scan/fetch when "between" happens as opposed to a "=" query which would imply severe performance degradations in specific cases. Perhaps this can be addressed at adapter level or as a configuration option? On Monday, March 18, 2013 7:27:09 AM UTC+1, Godfrey Chan wrote: > > Since this is a perf PR, I think it'd be nice to see some benchmarks to be > absolutely sure. > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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/rubyonrails-core?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
