Message-ID: <gh-pgjdbc-pgjdbc-3220-c2100495311@github.com>
From: "vlsi (@vlsi)" <noreply+vlsi@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Wed, 08 May 2024 12:43:52 +0000
Subject: Re: [pgjdbc/pgjdbc] PR #3220:  setTimestamp use timestamptz db type
In-Reply-To: <gh-pgjdbc-pgjdbc-3220@github.com>
References: <gh-pgjdbc-pgjdbc-3220@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: vlsi
X-GitHub-Comment-Id: 2100495311
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3220
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/pull/3220#issuecomment-2100495311
Content-Type: text/plain; charset=utf-8

>I can provide even more examples of problems if necessary

It would be great. I would suggest we solve problem a time rather than combine everything possible within a single discussion.

> Within the class TimestamptzTest, there are basic examples of statements that will fail if a timestamp parameter is passed as a string.

There are cases like `select ?` and `select pg_typeof(?)`, and I believe they are not quite niche, so we should not consider them as the primary driving factor.