Re: BUG #15904: ERROR: argument of LIMIT must not contain variables - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: BUG #15904: ERROR: argument of LIMIT must not contain variables
Date
Msg-id CAKFQuwZLr0QBB-HeteQ8fD+iVLNyjNDMwYKQ+CH=ZKps76_rrw@mail.gmail.com
Whole thread Raw
In response to BUG #15904: ERROR: argument of LIMIT must not contain variables  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #15904: ERROR: argument of LIMIT must not contain variables  (Lakradi Marwan <lakradimarwan@gmail.com>)
List pgsql-bugs
On Thu, Jul 11, 2019 at 8:06 AM PG Bug reporting form <noreply@postgresql.org> wrote:
The following bug has been logged on the website:

Bug reference:      15904
Logged by:          Lakradi Marwan
Email address:      lakradimarwan@gmail.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.

pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #15904: ERROR: argument of LIMIT must not contain variables
Next
From: Lakradi Marwan
Date:
Subject: Re: BUG #15904: ERROR: argument of LIMIT must not contain variables