Re: Timestamp Conversion Woes Redux

From: Oliver Jowett <oliver(at)opencloud(dot)com>
To: Dave Cramer <pg(at)fastcrypt(dot)com>
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Timestamp Conversion Woes Redux
Date: 2005-07-19 13:22:11
Message-ID: 42DCFE83.4060505@opencloud.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Dave Cramer wrote:

> setString is "special" because historically this is what we see in the
> upgrade problems. People try to insert a date using setString
> ('dateval') etc.

And we're back to: I think the right solution here is for people to fix
their broken apps, not to introduce unpredictable behaviour in the driver.

> Also we have historically told people to use setString to insert pg specific types, when there was no corresponding java type.

That's a fair point.

We really need a proper way for specifying this anyway; I had a trivial
PGobject implementation at one point that did the trick, but Kris didn't
like the other bits I did in that patch and I never got around to
implementing it separately.

-O

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Tom Lane 2005-07-19 13:54:19 Re: Timestamp Conversion Woes Redux
Previous Message Dave Cramer 2005-07-19 13:18:35 Re: Timestamp Conversion Woes Redux