Re: Timestamp Conversion Woes Redux

Dave Cramer wrote:

> You are correct, the driver is binding it to a timestamptz. The
> underlying data is without
> timezone so the server probably attempts to remove it
>
> I'm starting to think that binding the type to "unknown" might be
> better as you suggested earlier.

Yeah, given that we can't work out which of the two types is intended
ahead of time, this might be the best idea..

Christian, you should be able to test this easily enough by modifying
setTimestamp() to pass Oid.UNKNOWN instead of Oid.TIMESTAMPTZ to
bindString().

-O