| From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
|---|---|
| To: | Oliver Jowett <oliver(at)opencloud(dot)com> |
| Cc: | Csaba Nagy <nagy(at)ecircle-ag(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Christian Cryder <c(dot)s(dot)cryder(at)gmail(dot)com>, Postgres JDBC <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: Timestamp Conversion Woes Redux |
| Date: | 2005-07-19 23:08:43 |
| Message-ID: | DFF305E9-BD3B-47DA-BA3E-451DD5368EBB@fastcrypt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Christian is perfectly happy with
a PGTimestamp, and a PGTimestamptz type.
I did some research and Oracle has an extended PreparedStatement, which
implements
setTimestamp, and setTimestamptz, so I imagine they have run into the
same issues
Dave
On 19-Jul-05, at 6:59 PM, Oliver Jowett wrote:
> Dave Cramer wrote:
>
>> For that matter we could use a PGUnknown type as well.
>>
>
> This is exactly what the patch I mentioned earlier did, IIRC.
>
> -O
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeffrey Tenny | 2005-07-19 23:11:39 | Re: Timestamp Conversion Woes Redux |
| Previous Message | Oliver Jowett | 2005-07-19 23:08:30 | Re: Streaming ResultSet |