On 12/5/24 20:39, Daniele Varrazzo wrote:
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:
On Fri, 6 Dec 2024 at 02:27, Daniel Johnson wrote:
>
> Good day! I've run into a quirk executing an SQL statement and am not
> sure if it's a fundamental issue with my query or a bug in psycopg3.
It's a mix of an issue with your query, postgres being too forgiving
in parsing the interval, and ps
On 12/5/24 18:00, Adrian Klaver wrote:
On 12/5/24 17:37, Adrian Klaver wrote:
On 12/5/24 17:27, Daniel Johnson wrote:
You might try something like:
NOW() + INTERVAL || ' ' || %(NextDBLog)s || ' SECOND'
If that does work then you will need to use the psycopg.sql module to
build that part o
On 12/5/24 17:37, Adrian Klaver wrote:
On 12/5/24 17:27, Daniel Johnson wrote:
Good day! I've run into a quirk executing an SQL statement and am not
sure if it's a fundamental issue with my query or a bug in psycopg3.
In short, I'm inserting/updating a row using both NOW() and 'NOW()
plus a
On 12/5/24 17:27, Daniel Johnson wrote:
Good day! I've run into a quirk executing an SQL statement and am not
sure if it's a fundamental issue with my query or a bug in psycopg3.
In short, I'm inserting/updating a row using both NOW() and 'NOW() plus
a varying value'. The NOW() value is fine
