From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
---|---|
To: | Oliver Jowett <oliver(at)opencloud(dot)com> |
Cc: | Ravi Periasamy <ravitx12(at)yahoo(dot)com>, pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: issues with Statement.getTimestamp(int, Calendar) |
Date: | 2006-12-13 13:58:36 |
Message-ID: | 59C2537D-6B49-410E-A674-D97A333D7F65@fastcrypt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Oliver,
To be honest, I didn't write the stuff in AbstractJdbc2Statement.
That is left over from the original implementation. That being said,
there is no function in the utils that takes a date and a calendar
and returns a Calendar.
It does look like the best place to put that code though.
Dave
On 13-Dec-06, at 7:28 AM, Oliver Jowett wrote:
> Ravi Periasamy wrote:
>
>> I suspect the AbstractJdbc2Statement.changetime()
>> method.
>
> Yeah, that code looks pretty broken to me, it has completely the
> wrong end of the stick about what it should be doing with the
> provided calendar, AFAICS.
>
> Dave, why doesn't the out-parameter stuff do timestamp conversion
> by delegating to the same code as the ResultSet code uses? That
> does all the hard stuff for you..
>
> -O
>
From | Date | Subject | |
---|---|---|---|
Next Message | David Nedrow | 2006-12-13 17:09:33 | String escaping? |
Previous Message | Oliver Jowett | 2006-12-13 12:28:19 | Re: issues with Statement.getTimestamp(int, Calendar) |