From: | Mathias Picker <Mathias(dot)Picker(at)virtual-earth(dot)de> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | postgres 7.4.2: float(20) results in error msg, but should not since 7.4) |
Date: | 2004-04-03 12:54:40 |
Message-ID: | 406EB410.8070400@virtual-earth.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
While trying to install the roundup issue tracking system I discovered
the following - faulty - behaviour:
My fresh postgres 7.4.2 install on a FreeBSD 5.2-CURRENT machine replies
"ERROR: precision for FLOAT must be less than 16"
to
"create table otks (otk_key varchar(255),otk_value
varchar(255),otk_time float(20));"
Now http://www.postgresql.org/docs/7.4/static/datatype.html#DATATYPE-FLOAT
says
"PostgreSQL accepts float(1) to float(24) as selecting the real type,
while float(25) to float(53) select double precision."
and
"Note: Prior to PostgreSQL 7.4, the precision in float(p) was taken to
mean so many decimal digits. This has been corrected to match the SQL
standard, which specifies that the precision is measured in binary digits."
So it should work, I guess. Are there any switches to alter this
behaviour, or is this a bug??
Thanks, Mathias
From | Date | Subject | |
---|---|---|---|
Next Message | Janning Vygen | 2004-04-03 12:59:42 | Re: Checking FKs after COPY and disabled Triggers |
Previous Message | Rajat Katyal | 2004-04-03 08:38:44 | Problem in calling prepare statement from STORED PROCEDURE |