BUG #17527: Timestamp bind variable using 0000-00-00, 0000/00/00

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: jhlee(at)warevalley(dot)com
Subject: BUG #17527: Timestamp bind variable using 0000-00-00, 0000/00/00
Date: 2022-06-22 02:27:33
Message-ID: 17527-76912eafe534d095@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 17527
Logged by: Lee Jae Hyun
Email address: jhlee(at)warevalley(dot)com
PostgreSQL version: 10.3
Operating system: Windows 10
Description:

I would like to inform you that it is being used in Korea and has been
translated into Korean -> English through a translator.

Question about variable binding failure for timestamp column in postgresql

The test was conducted on ODBC Drvier 13.00.00.00, and the server is the
same as the 11.7 and 10.3 versions.

1. Sample Data

create table t1 (data timestamp);
insert into t1 ( data ) values ( ? );
-- Bind variable ( 2022-06-22) successful;
-- Bind variable (2022/06/22) failed;

Can bind variables in 0000/00/00 format be used in ODBC? Or, I would like to
ask if it is possible to use only bind variables of 0000-00 unconditionally.

Browse pgsql-bugs by date

  From Date Subject
Next Message Noah Misch 2022-06-22 03:37:04 Re: Extension pg_trgm, permissions and pg_dump order
Previous Message PG Bug reporting form 2022-06-22 01:59:27 BUG #17526: PG_DUMP is not outputting "CREATE SCHEMA" statements when an extension is assigned to a schema