From: Tom Lane <tgl@sss.pgh.pa.us>
To: Matthew Bellew <matthewb@labkey.com>
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: Parameter marker swapping in {fn timestampdiff()}
In-reply-to: 
 <CAJnjrPND0MiidV+zRgzmL4zb5oYv9TgCUwtYqD4yW3+k4Cc+Cg@mail.gmail.com>
References: 
 <CAJnjrPND0MiidV+zRgzmL4zb5oYv9TgCUwtYqD4yW3+k4Cc+Cg@mail.gmail.com>
Comments: In-reply-to Matthew Bellew <matthewb@labkey.com>
	message dated "Sun, 26 Mar 2023 11:14:44 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3016275.1679856879.1@sss.pgh.pa.us>
Date: Sun, 26 Mar 2023 14:54:39 -0400
Message-ID: <3016276.1679856879@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/3016276.1679856879%40sss.pgh.pa.us>
Precedence: bulk

Matthew Bellew <matthewb@labkey.com> writes:
> I recently made a small change to a core utility and our sql tests flagged
> some unexpected results.  I traced these to timestampdiff().  Below is a
> running code function (except for creating the JDBC Connection).  I expect
> the same result for all three executeQuery() calls.  The version that uses
> string literals return 366 and the versions that use parameter markers
> return -366.

You probably want to report that on the pgsql-jdbc list.  This list
mainly deals in bugs in core Postgres, so I'm not very sure whether
the JDBC maintainers read it.

			regards, tom lane