From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
---|---|
To: | Kris Jurka <books(at)ejurka(dot)com> |
Cc: | Oliver Jowett <oliver(at)opencloud(dot)com>, "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: getXXX methods |
Date: | 2004-07-07 19:53:50 |
Message-ID: | 1089230030.1506.226.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Ok, it appears (at least from my understanding) that Kris is correct
here.
I had a look at the sql2003 proposed spec (ISO/IEC 9075-2:2003(E)), and
it states:
A number is assignable only to sites of numeric type. If an assignment
of some number would result in a loss of it's most significant digit, an
exception conditions is raised. If least significant digits are lost,
implementation defined rounding, or truncation occurs, with no exception
condition being raised.
Dave
On Tue, 2004-07-06 at 21:58, Kris Jurka wrote:
> On Wed, 7 Jul 2004, Oliver Jowett wrote:
>
> > > How many people really check for warnings anyway?
> >
> > I hate this argument. If we don't generate any warnings, of course no
> > one will check for them!
>
> No, this is different. Exceptions are supposed to prevent you from
> checking the return code on every function call, which the warning API
> seems to want to you to do.
>
> Kris Jurka
>
>
>
> !DSPAM:40eb58bf196361343028809!
>
>
--
Dave Cramer
519 939 0336
ICQ # 14675561
From | Date | Subject | |
---|---|---|---|
Next Message | Kris Jurka | 2004-07-08 06:37:27 | Re: no link in GBorg |
Previous Message | Bill Chandler | 2004-07-07 16:16:40 | Terrible performance after deleting/recreating indexes |