Why so? I thought if driver will pass timestamp with tz some queries won't work because of lack of implicit conversion, but I don't understand how can it corrupt anything.
> I've made a blunt stab at working around the issue. > The attached patch adds a new parameter to the JDBC URL: timestamp. > The parameter can be wither 'with_timezone' or 'without_timezone'. If > the parameter is missing, or has a different value then the current > behaviour (using Oid.UNSPECIFIED) is exhibited. With the parameters > specified correctly one of the Oid.TIMESTAMP or Oid.TIMESTAMPTZ is > used when sending Timestamp arguments to the server.
This won't really work in general though. If you have a database that has both timestamp and timestamptz fields in it, there is no valid setting of this configuration option. Setting it either way will result in silent corruption of your data.
