From: Ken Kachnowich <khkachn@madweed.ncsc.mil>
To: postgres interfaces <pgsql-interfaces@hub.org>
Subject: RE: datetime fix
Date: Mon, 30 Oct 2000 15:06:13 +0000
Message-ID: <39FD8E65.4FED4534@madweed.ncsc.mil> (raw)
The Timestamp problem seems to be with the backend truncating the
millseconds to 2 digits.
Here are the (abreviated) results from my test queries:
Inserting record:
query: insert into table_a values (91, '2000-10-30 09:19:57.321')
psql select:
my_db=# select * from table_a;
id | message_time
--+----------------------
91 | 2000-10-30 09:19:57.32-05
Note the milleseconds were truncated from .321 to .32
Result from JDBC select of Timestamp field:
91 | 2000-10-30 09:19:57.032
The Timestamp field has been padded to 3 digits but started out with an
incorrect value.
Could I have something set wrong to cause this or is this a bug?
Thanks,
Ken
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-interfaces@postgresql.org
Cc: khkachn@madweed.ncsc.mil, pgsql-interfaces@hub.org
Subject: RE: datetime fix
In-Reply-To: <39FD8E65.4FED4534@madweed.ncsc.mil>
* 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