Pete Beck wrote:
On Tue, 2003-01-14 at 04:32, Dain Sundstrom wrote:
Postgres can't store millisecond accurate time until 7.0. Before that
it truncates it to a decasecond if I remember.
-dain
Besides which, you're crazy if your not using a more recent version of
Postgres as since 7.1 i
On Tue, 2003-01-14 at 04:32, Dain Sundstrom wrote:
> Postgres can't store millisecond accurate time until 7.0. Before that
> it truncates it to a decasecond if I remember.
>
> -dain
Besides which, you're crazy if your not using a more recent version of
Postgres as since 7.1 it has improved dram
Postgres can't store millisecond accurate time until 7.0. Before that
it truncates it to a decasecond if I remember.
-dain
On Monday, January 13, 2003, at 05:06 PM, Eric Klimas wrote:
I don't think this is as much a Jboss issue as it might be a Postgres
JDBC driver issue. I experienced this o
ayson" <[EMAIL PROTECTED]>
To: "jboss user" <[EMAIL PROTECTED]>
Sent: Monday, January 13, 2003 2:41 PM
Subject: [JBoss-user] cmp2, postgres and dates
> Hi,
>
> I am experiencing a problem with dates:
>
> jboss304tomcat406:
>
> A 'new Dat
I don't think this is as much a Jboss issue as it might be a Postgres
JDBC driver issue. I experienced this once before on Postgres 6.x
(probably 6.2). I recently experimented again with a newer driver on
Postgres 7.x and the problem seems to have gone away.
Unfortunately, I can't offer much mor
Hi,
I am experiencing a problem with dates:
jboss304tomcat406:
A 'new Date()' passed to an abstract cmp setter sets the date with a
millisecond value in the postgres table column. When it does this, it
doesn't give it back to me using the getter. The workaround is the
reformat the date (using
