make count(:conditions => {}) work on has_many associations
Reported by Jan De Poorter | May 28th, 2008 @ 08:01 PM
When using conditions from a variable, it can sometimes be an empty hash (at least in my projects). When using it with count on a ActiveRecord::Base:
User.count :conditions => {}
# => 3
But when working on a has_many association, this happens:
>> User.first.certificates.count :conditions => {}
ActiveRecord::StatementInvalid: Mysql::Error: #42000You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '))' at line 1: SELECT count(*) AS count_all FROM `certificates` WHERE (`certificates`.user_id = 442758120 AND ())
a patch to fix this has been attached
Comments and changes to this ticket
-
Repository May 29th, 2008 @ 11:11 AM
(from [abb1bd2efa43b8efbb3faf4ccfb9246704a9044c]) Ensure AssociationCollection#count works with empty condition. [#271 state:resolved] [Jan De Poorter]
-
Pratik May 29th, 2008 @ 12:30 PM
- → State changed from “new” to “resolved”
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Source available from github
Repository is at http://github.com/rails/rails
Check out the development master (Edge Rails):
git clone git://github.com/rails/rails.git
Creating or reviewing a patch
See the contributor guide.
Creating a feature request
Please don't. If you want a new feature in Rails, you'll have to pull up your sleeves and get busy yourself. Or convince someone else to do it. See the contributor guide on how to get going. But posting them here is just going to lead to ticket root.
Creating a bug report
When creating a bug report, be sure to include as much relevant information as possible. Post the code sample that causes the problem. Preferably, alter the unit tests and show through either changed or added tests how the expected behavior is not occuring.
Security vulnerabilities should be reported via an email to security@rubyonrails.org, do not use trac for reporting security vulnerabilities. All content in trac is publicly available as soon as it is posted.
Then don't get your hopes up. Unless you have a "Code Red, Mission Critical, The World is Coming to an End" kinda bug, you're creating this ticket in the hope that others with the same problem will be able to collaborate with you on solving it. Do not expect that the ticket automatically will see any activity or that others will jump to fix it. Creating a ticket like this is mostly to help yourself start on the path of fixing the problem and for others to sign on to with a "I'm having this problem too"..
