This project is archived and is in readonly mode.
chaining named_scopes that use ActiveRecord::QueryMethods with default_scope doesnt work
Reported by shoreside | November 16th, 2010 @ 01:08 PM
When you use a named scope that uses one of the ActiveRecord::QueryMethods like order('foo ASC') on a model that has a default_scope defined that receives a lambda or a proc, the scope evaluates the lambda of the default_scope only on the first invocation and seems to cache the resulting query. The chaining works when using hash options instead of query methods, e.g. :order => 'foo ASC'.
We attached a patch that provides two test methods, one for the query methods and one for the hash options example to reproduce the error. We'd like to use default_scope for a multi-tenant solution. Thanks in advance for any help!
Best,
Christian
Comments and changes to this ticket
-
rails February 17th, 2011 @ 12:00 AM
- State changed from “new” to “open”
This issue has been automatically marked as stale because it has not been commented on for at least three months.
The resources of the Rails core team are limited, and so we are asking for your help. If you can still reproduce this error on the 3-0-stable branch or on master, please reply with all of the information you have about it and add "[state:open]" to your comment. This will reopen the ticket for review. Likewise, if you feel that this is a very important feature for Rails to include, please reply with your explanation so we can consider it.
Thank you for all your contributions, and we hope you will understand this step to focus our efforts where they are most helpful.
-
rails February 17th, 2011 @ 12:00 AM
- State changed from “open” to “stale”
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>
shoreside