This project is archived and is in readonly mode.
find_last_by_* dynamic finder
Reported by Lawrence Pit | July 15th, 2008 @ 02:51 AM | in 2.x
This patch allows the following:
Account.find_last_by_limit(50)
Account.find_first_by_limit(50)
Comments and changes to this ticket
-
Tarmo Tänav July 15th, 2008 @ 03:41 AM
I think you forgot to remove the old implementation of determine_finder().
I'm not sure if find_first_by is a good addition though because one would need to decide between using find_by and find_first_by and in this case a choice creates confusion (ie. do you use 'first_by' because it is more explicit and communicates the meaning of the code better of 'by' because it's shorter, easier to read/write).
-
-
Pratik July 17th, 2008 @ 12:56 AM
- State changed from “new” to “wontfix”
I don't really think this is needed and will be useful. But please do continue the discussion in mailing list if you think it's really useful.
Thanks.
-
Ryan Bigg October 11th, 2010 @ 10:53 AM
- Tag cleared.
- Importance changed from “” to “Low”
Automatic cleanup of spam.
-
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>
Jeff Kreeftmeijer
Jeremy Kemper
Pratik
Ryan Bigg
Tarmo Tänav