From: | Daniel Serodio <daniel(at)checkforte(dot)com(dot)br> |
---|---|
To: | PostgreSQL JDBC List <pgsql-jdbc(at)postgresql(dot)org> |
Cc: | Mike Bridge <mike(at)bridgecanada(dot)com> |
Subject: | Re: Using 7.1 driver with 7.3? |
Date: | 2002-12-23 19:57:00 |
Message-ID: | 1040673424.6081.66.camel@kelly |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On Mon, 2002-12-23 at 17:37, Tom Lane wrote:
> Mike Bridge <mike(at)bridgecanada(dot)com> writes:
> > The version of a proprietary library we have licensed does not
> > understand the extra decimal places in Postgresql 7.3 datetime
> > types. (We are currently using it with Postgresql 7.1.) But
> > everything else appears to work fine with the new 7.3 jdbc driver.
>
> Why don't you just declare your timestamp columns as timestamp(0),
> so that the extra decimal places are suppressed?
Most likely because the DB is already being used in production. I ran
into this problem when upgrading our DB admin upgraded our server from
7.1 to 7.2, without letting us know.
We upgraded the driver to 7.2 and it worked, but I really cursed
whoever thought that changing the default behaviour of a timestamp
column was a good idea.
It's a PITA, but I think your best bet is to make a full ASCII dump of
your DB, replace 'timestamp' with 'timestamp (0)' and recreate it.
Good luck, and let us know of the outcome.
> > I've tested our stuff with the old driver and the new database, and
> > it appears to work. My question is: is this a good idea?
>
> I doubt it. There have been a heck of a lot of bug fixes in the JDBC
> driver since 7.1, so even if there aren't any compatibility issues to
> worry about (which seems unlikely), it would be much better to use the
> up-to-date driver.
>
> regards, tom lane
>
--
[]'s
Daniel Serodio
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Lamb | 2002-12-23 20:52:18 | Re: Using 7.1 driver with 7.3? |
Previous Message | Dave Cramer | 2002-12-23 19:52:31 | Re: Using 7.1 driver with 7.3? |