Message-ID: <3143b3b4-c22c-4fed-ab6c-aa371a3cd288@progman.us>
Date: Fri, 6 Dec 2024 17:21:10 -0600
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Parameter in SQL query being misinterpreted
To: psycopg@lists.postgresql.org
References: <dfc11d8e-dc27-4c72-a2aa-87b2150dc331@progman.us>
 <CA+mi_8YTTz0CXGRgrp9+DF-gNJZ5+Wv2uiMYYLO5UbTtZUi2Sw@mail.gmail.com>
Content-Language: en-US
From: Daniel Johnson <djohnson@progman.us>
In-Reply-To: 
 <CA+mi_8YTTz0CXGRgrp9+DF-gNJZ5+Wv2uiMYYLO5UbTtZUi2Sw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/3143b3b4-c22c-4fed-ab6c-aa371a3cd288%40progman.us>
Precedence: bulk

On 12/5/24 20:39, Daniele Varrazzo wrote:
<snip>
> Adrian has already provided a few workarounds for the problem you
> report - thank you very much!. The one I prefer is however the
> following, because it does without string operations: it makes use of
> the possibility to multiply an interval by a scalar:
> 
>      >>> cur.execute("select now(), now() + %s * '1 second'::interval",
> (10,)).fetchone()
>      (datetime.datetime(2024, 12, 6, 2, 33, 32, 117134,
> tzinfo=zoneinfo.ZoneInfo(key='Europe/London')),
>       datetime.datetime(2024, 12, 6, 2, 33, 42, 117134,
> tzinfo=zoneinfo.ZoneInfo(key='Europe/London')))

Oh I hadn't even thought about multiplying an interval, that's a very 
clean approach.  Prior to e-mailing the list I'd tried something similar 
to (but not as thorough as) Adrian's suggestion and it had failed, but 
if it works I like the look of this.

I vaguely recall having a similar interval manipulation headache in a 
PHP portion of this project, I shall try the same thing there.

Thank you so much!

Daniel Johnson
djohnson@progman.us