| From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
|---|---|
| To: | Oliver Jowett <oliver(at)opencloud(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Christian Cryder <c(dot)s(dot)cryder(at)gmail(dot)com>, pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: Timestamp Conversion Woes Redux |
| Date: | 2005-07-19 12:32:32 |
| Message-ID: | E14D759B-135D-4531-9322-9F4C535C2627@fastcrypt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Oliver,
Can you explain your rationale ?
Mine is:
The overhead isn't that bad.
Anyone using the API correctly will not be affected ( assuming they
use setInt() etal correctly )
Philosophically speaking, making the driver more strict does not make
it easier for people to convert to postgresql. AFAICT, most drivers
tend to be more lenient.
Dave
On 19-Jul-05, at 8:23 AM, Oliver Jowett wrote:
> Dave Cramer wrote:
>
>> I'm also thinking we should use UNKOWN for setString as well,
>> hopefully this would reduce the number of upgrade problems people
>> are having when they upgrade from 7.x to 8.x
>>
>
> I still think this is a bad idea.
>
> -O
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oliver Jowett | 2005-07-19 12:45:11 | Re: Timestamp Conversion Woes Redux |
| Previous Message | Oliver Jowett | 2005-07-19 12:23:37 | Re: Timestamp Conversion Woes Redux |