No, its not a bug, the sql generated by the :first option returns whatever results matches it can be any record. It is the SQL that behaves this way, it is not Rails fault.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| rails bug: incorrect sql generated or no error checking performed | 1 | 159 | September 20, 2006 | |
| Self-referential HABTM SQL mal-formed when updating record | 0 | 114 | January 23, 2008 | |
| Strange behaviour | 4 | 101 | November 17, 2008 | |
| sql question | 0 | 95 | December 7, 2008 | |
| HABTM join table quirk | 0 | 127 | December 9, 2006 |