From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | lakradimarwan(at)gmail(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: BUG #15904: ERROR: argument of LIMIT must not contain variables |
Date: | 2019-07-11 15:27:44 |
Message-ID: | CAKFQuwZLr0QBB-HeteQ8fD+iVLNyjNDMwYKQ+CH=ZKps76_rrw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Thu, Jul 11, 2019 at 8:06 AM PG Bug reporting form <
noreply(at)postgresql(dot)org> wrote:
> The following bug has been logged on the website:
>
> Bug reference: 15904
> Logged by: Lakradi Marwan
> Email address: lakradimarwan(at)gmail(dot)com
> PostgreSQL version: 11.4
> Operating system: Mac OS X - High Sierra
> Description:
>
> I don't see the point, what is the main difference between
> summary.amount_summed which is a float, and directly pass 100.0 ?
>
A limit applies to the query as a whole and cannot depend on individual
records. If you think that is wrong explain what the following query is
supposed to return and why.
SELECT *
FROM (VALUES (1, 'one'), (2, 'two')) vals (i, t)
LIMIT CASE WHEN vals.i = 1 THEN 1 ELSE 2 END;
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Lakradi Marwan | 2019-07-11 16:26:41 | Re: BUG #15904: ERROR: argument of LIMIT must not contain variables |
Previous Message | PG Bug reporting form | 2019-07-11 15:05:29 | BUG #15904: ERROR: argument of LIMIT must not contain variables |