From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: jhlee@warevalley.com
Subject: BUG #17527: Timestamp bind variable using 0000-00-00, 0000/00/00
Date: Wed, 22 Jun 2022 02:27:33 +0000
Message-ID: <17527-76912eafe534d095@postgresql.org> (raw)
The following bug has been logged on the website:
Bug reference: 17527
Logged by: Lee Jae Hyun
Email address: jhlee@warevalley.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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, jhlee@warevalley.com
Subject: Re: BUG #17527: Timestamp bind variable using 0000-00-00, 0000/00/00
In-Reply-To: <17527-76912eafe534d095@postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox