=?utf-8?q?Rados=C5=82aw_Smogura?= <rsmog...@softperience.eu> writes:
> I work on binary support for JDBC. I saw disadventage of TIMESTAMPS WITH /
> WITHOUT TZ. Currently (in text mode) driver always sends date time string
> with
> appended time offset, as UNSPECIFIED so backend can choose to use offset or
> not. In binary mode I can only send 8 bytes timestamp without appended
> timezone. This timestamp must be properly encoded depending if target is WITH
> TZ or not, but JDBC (and other clients, probably too) doesn't have any
> knowledge about target type when statement is executed
Seems like you need to fix *that*.
> I think about following patch (giving backward compatibility) on timestamp
> (tz). Idea is as follows if we have additional two bytes it's TZ offset and
> use this to convert received time to UTC. I wrote it in e-mail editor (sorry
> :) no C IDE last time),
This is not a terribly good idea, and even if it was, how will you use
it from a client that doesn't know which data type is really in use?
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
