This project is archived and is in readonly mode.
Named Scope test should not assume SQL order
Reported by CancelProfileIsBroken | December 30th, 2008 @ 01:17 AM | in 2.x
Attached patch fixes test_should_use_where_in_query_for_named_scope, which assumed that two different SQL SELECT statements would return records in the same order, even without an ORDER BY. This was failing on sqlite2 (only). With this patch, AR tests for named scope pass across all database types we ship.
Comments and changes to this ticket
-
Repository December 30th, 2008 @ 03:18 AM
- State changed from “new” to “resolved”
(from [a29369ae4ac705fbbd4ac0c0325468e50e4eeca0]) Fix named scope tests for sqlite3 [#1667 state:resolved]
Signed-off-by: Pratik Naik pratiknaik@gmail.com http://github.com/rails/rails/co...
-
Repository February 2nd, 2009 @ 07:57 PM
(from [feb807dda1c2f13aadf01ea17bd9bfb3c6a401e0]) Fix named scope tests for sqlite3 [#1667 state:resolved]
Signed-off-by: Pratik Naik pratiknaik@gmail.com http://github.com/rails/rails/co...
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>
People watching this ticket
CancelProfileIsBroken
Pratik
Attachments
Tags
Referenced by
-
1667
Named Scope test should not assume SQL order
(from [a29369ae4ac705fbbd4ac0c0325468e50e4eeca0]) Fix nam...
-
1667
Named Scope test should not assume SQL order
(from [feb807dda1c2f13aadf01ea17bd9bfb3c6a401e0]) Fix nam...