Message-ID: <gh-pgjdbc-pgjdbc-3220-c2100604964@github.com>
From: "vlsi (@vlsi)" <noreply+vlsi@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Wed, 08 May 2024 13:40:14 +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: 2100604964
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-2100604964
Content-Type: text/plain; charset=utf-8

> testTypeOnDbSite_functionOverloading

Currently it defines a function with `timestmaptz`, and a function with `text` parameters.

I would suggest adding `timestamp` (without tz), `time`, and `timetz` into the mix and suggest the way you would expect it to work.

Frankly speaking, I think `setTimestmap( new Timestamp(..))` should fail rather than arbitrary select `timestamptz` overload among `timestamp` and `timestamptz`.