From 45f4282149e13a2c1548a579f60d098e397a33d7 Mon Sep 17 00:00:00 2001 From: Kevin Marsh Date: Thu, 10 Dec 2020 11:28:55 -0800 Subject: [PATCH] Refs #31792 -- Updated SQL example in Exists() docs. Follow up to 51297a92324976a704279b567ec4f80bb92d7b60. --- docs/ref/models/expressions.txt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/ref/models/expressions.txt b/docs/ref/models/expressions.txt index 0c6ff1e79ee..51addc4812f 100644 --- a/docs/ref/models/expressions.txt +++ b/docs/ref/models/expressions.txt @@ -633,12 +633,13 @@ On PostgreSQL, the SQL looks like: .. code-block:: sql SELECT "post"."id", "post"."published_at", EXISTS( - SELECT U0."id", U0."post_id", U0."email", U0."created_at" + SELECT (1) as "a" FROM "comment" U0 WHERE ( U0."created_at" >= YYYY-MM-DD HH:MM:SS AND - U0."post_id" = ("post"."id") + U0."post_id" = "post"."id" ) + LIMIT 1 ) AS "recent_comment" FROM "post" It's unnecessary to force ``Exists`` to refer to a single column, since the