Message-ID: From: "BbIKTOP (@BbIKTOP)" To: "pgjdbc/pgjdbc" Date: Mon, 20 Jan 2025 08:55:51 +0000 Subject: Re: [pgjdbc/pgjdbc] issue #3482: When using java.sql.Timestamp for update, an exception thrown In-Reply-To: References: List-Id: X-GitHub-Author-Login: BbIKTOP X-GitHub-Comment-Id: 2601796706 X-GitHub-Comment-Type: issue_comment X-GitHub-Issue: 3482 X-GitHub-Repo: pgjdbc/pgjdbc X-GitHub-Type: comment X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/3482#issuecomment-2601796706 Content-Type: text/plain; charset=utf-8 Well, Dave, as a developer for about last 40 years, I totally understand your point ;) I mean "it's somewhere someone's else problem" I did that so many times as well ) Please understand mine. As soon as this: ``` root@d2c635331de7:/# psql localdev dev psql (17.2 (Debian 17.2-1.pgdg120+1)) Type "help" for help. localdev=> merge into localdev.test as dst using (select 3 as "id", to_timestamp('2025-01-18 08:39:48', 'YYYY-MM-DD hh24:mi:ss') at time zone 'EET' as "ts", 44 as amount) src on dst."id"=src.id when matched then update set "ts"=src."ts", amount=src."amount" when not matched then insert ("id", "ts", "amount") values (src."id", src."ts", src."amount") ; MERGE 1 localdev=> ``` works, I still insist it is a driver's problem. I could make a simple C program to check, but as for me it is quite obvious, isn't it?