This project is archived and is in readonly mode.
Named Scope test should not assume SQL order
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.
-
named_scope_test_patch.diff
961 Bytes
-
Repository- State changed from new to resolved
(from [a29369ae4ac705fbbd4ac0c0325468e50e4eeca0]) Fix named scope tests for sqlite3 [#1667 Named Scope test should not assume SQL order state:resolved]
Signed-off-by: Pratik Naik pratiknaik@gmail.com http://github.com/rails/rails/co...
-
Repository
(from [feb807dda1c2f13aadf01ea17bd9bfb3c6a401e0]) Fix named scope tests for sqlite3 [#1667 Named Scope test should not assume SQL order state:resolved]
Signed-off-by: Pratik Naik pratiknaik@gmail.com http://github.com/rails/rails/co...