MIME-Version: 1.0
Date: Sat, 19 Mar 2022 13:10:54 +0100
From: Paolo De Stefani <paolo@paolodestefani.it>
To: Christophe Pettus <xof@thebuild.com>
Cc: Psycopg <psycopg@postgresql.org>
Subject: Re: Query with boolean parameter
In-Reply-To: <74FC637F-2D25-4CD0-A075-9CB5293FCA5B@thebuild.com>
References: <8df15d1263aaa1a9d36eacb0e5b9a28e@paolodestefani.it>
 <74FC637F-2D25-4CD0-A075-9CB5293FCA5B@thebuild.com>
User-Agent: Roundcube Webmail/1.4.12
Message-ID: <d88ac5f2ae2457bb2b97f98c47cfcdfc@paolodestefani.it>
Content-Type: text/plain; charset=US-ASCII;
 format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/d88ac5f2ae2457bb2b97f98c47cfcdfc%40paolodestefani.it>
Precedence: bulk

Il 19/03/2022 01:00 Christophe Pettus ha scritto:
>> On Mar 18, 2022, at 16:56, Paolo De Stefani <paolo@paolodestefani.it> 
>> wrote:
>> Is there any reason why the second query results in a syntax error?
> 
> There's not IS operator in PostgreSQL (or in SQL).  IS NULL, IS NOT
> NULL, IS TRUE, and IS FALSE are in effect unary postfix operators, so
> you can't construct them that way via parameter substitution.

Thanks, i see

The problem is (for me) that with psycopg2 this works:
cur.execute('SELECT * FROM system.app_user WHERE can_edit_views IS 
TRUE')
cur.execute('SELECT * FROM system.app_user WHERE can_edit_views IS %s', 
(True,))
cur.execute('SELECT * FROM system.app_user WHERE can_edit_views IS %s', 
(None,))

Switching to psycopg 3 i have to consider many more differences than i 
expected

-- 
Paolo De Stefani