From: | "Maurice Gittens" <mgittens(at)gits(dot)nl> |
---|---|
To: | "Andreas Zeugswetter" <andreas(dot)zeugswetter(at)telecom(dot)at>, "'hackers(at)postgresql(dot)org'" <hackers(at)postgreSQL(dot)org> |
Subject: | Re: [HACKERS] float --> int |
Date: | 1998-05-11 13:27:52 |
Message-ID: | 007e01bd7ce0$99d91060$fcf3b2c2@caleb..gits.nl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
-----Original Message-----
From: Andreas Zeugswetter <andreas(dot)zeugswetter(at)telecom(dot)at>
To: 'hackers(at)postgresql(dot)org' <hackers(at)postgreSQL(dot)org>
Date: maandag 11 mei 1998 21:31
Subject: [HACKERS] float --> int
>Maurice wrote:
>> Making an int from a float is only defined for "small" values of the
float.
>> So for the general case such a conversion would simply overflow the int,
>> giving it an undefined value. Does this make sense to you?
>
>This sure sounds good:
>select (4.00000 !); -- would work, but
>select (4.30000 !); -- would throw a runtime error like
>ERROR: float to integer conversion error, value out of range.
>
I agree. I'm just trying to say that the error should be flagged as such.
Maurice
From | Date | Subject | |
---|---|---|---|
Next Message | Jose' Soares Da Silva | 1998-05-11 13:33:55 | money or dollar type |
Previous Message | Jose' Soares Da Silva | 1998-05-11 13:25:03 | Re: NEW ODBC DRIVER |