David Dodsworth ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
real or float4 '=' operator is broken in 7.1.2
Long Description
As the example shows, a select for on a 'real' or 'float4' value
value will not return any rows wh
More information to add to this bug.
I get the same behavior as the original poster, but the following on these
queries:
sszabo=> select myfloat-29.92 from "test_f4";
?column?
--
7.62939436071974e-08
7.62939436071974e-08
(2 rows)
sszabo=> select myfloat-'29.92
[EMAIL PROTECTED] writes:
> pg_dump doesn't handle CREATE FUNCTIONs well
Any particular version to mention with that?
AFAIK this is fixed in the current release (7.1.2)
regards, tom lane
---(end of broadcast)---
TIP 1: sub
I saw the problem in 2 different (but mirrored and therefore identical)
7.1.2 databases. The data was created in the db before 7.1.2 but it has
since been upgraded and the dump was via 7.1.2. Was the bug in the dump code
or did it have to do with db creation?
Thanks,
--Rainer
> -Original Me
[EMAIL PROTECTED] writes:
> real or float4 '=' operator is broken in 7.1.2
No, it isn't --- try coercing the values you are comparing against
to be float4. Your error is in assuming that 29.92::float8 should
equal 29.92::float4 coerced back to float8. Which might be a nice
property to have, but
Rainer Mager ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
pg_dump doesn't handle CREATE FUNCTIONs well
Long Description
We have a table (table_A) that has a constraint on it that uses a custom function
(func_B), which refer
Marcos ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
insert of date is wrong
Long Description
when I insert the date '1914/01/01' in a column with the 'date' format, the table
returns the value '1913/12/31'
Sample Code
in
