From 4ad4de50ce164f7b62661408eceb4259dfccdf66 Mon Sep 17 00:00:00 2001 From: Ryuta Kamizono Date: Thu, 7 Mar 2019 12:10:36 +0900 Subject: Correct the limitation about `order` with `distinct` in the guide That is happened with `distinct`, and that is not only happened on MyS L, but also on PostgreSQL, SQL Server, and Oracle. [ci skip] --- guides/source/active_record_querying.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'guides') diff --git a/guides/source/active_record_querying.md b/guides/source/active_record_querying.md index 30493038e7..c9db99ca1d 100644 --- a/guides/source/active_record_querying.md +++ b/guides/source/active_record_querying.md @@ -611,7 +611,8 @@ If you want to call `order` multiple times, subsequent orders will be appended t Client.order("orders_count ASC").order("created_at DESC") # SELECT * FROM clients ORDER BY orders_count ASC, created_at DESC ``` -WARNING: If you are using **MySQL 5.7.5** and above, then on selecting fields from a result set using methods like `select`, `pluck` and `ids`; the `order` method will raise an `ActiveRecord::StatementInvalid` exception unless the field(s) used in `order` clause are included in the select list. See the next section for selecting fields from the result set. + +WARNING: In most database systems, on selecting fields with `distinct` from a result set using methods like `select`, `pluck` and `ids`; the `order` method will raise an `ActiveRecord::StatementInvalid` exception unless the field(s) used in `order` clause are included in the select list. See the next section for selecting fields from the result set. Selecting Specific Fields ------------------------- -- cgit v1.2.3