Support join based eagerloading of has_one through associations
Reported by Frederick Cheung | August 25th, 2008 @ 11:23 PM | in 2.x
has_one :through currently only supports eager loading via the newer preload scheme. This patch enables use of the previous join based scheme
Comments and changes to this ticket
-
Frederick Cheung August 25th, 2008 @ 11:34 PM
- no changes were found...
-
Tarmo Tänav August 26th, 2008 @ 01:16 AM
Added another patch on top of this one that fixes join-based eager loading of has_one associations with more than one matching record and an order.
-
Repository August 26th, 2008 @ 05:27 AM
- → State changed from “new” to “resolved”
(from [6ae0a0557d5e2859e359275b5feebb7e3c13271c]) Load the first and not the last has_one result when doing join-based eager loading
This matters when the has_one is defined with an order in which case there is an expectation that the first one will be loaded.
[#904 state:resolved]
Signed-off-by: Jeremy Kemper jeremy@bitsweat.net http://github.com/rails/rails/co...
-
Repository August 26th, 2008 @ 05:27 AM
(from [a445cdd8840c4e99c40c6d5b15ab380d39a56be3]) Load the first and not the last has_one result when doing join-based eager loading
This matters when the has_one is defined with an order in which case there is an expectation that the first one will be loaded.
[#904 state:resolved]
Signed-off-by: Jeremy Kemper jeremy@bitsweat.net http://github.com/rails/rails/co...
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
The Git repository resides at http://github.com/rails
Check out the current development trunk (Edge Rails) with:
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".
