Tony Caduto <[EMAIL PROTECTED]> writes:
> I could have swore that this worked in earlier releases of Postgresql
> i.e. 7.4.
> CREATE TABLE public.test
> (
> junk double NOT NULL,
> CONSTRAINT junk_pkey PRIMARY KEY (junk)
> )WITHOUT OIDS;
> Now it gives a error that type double does not exist.
[ tries it... ] Sorry, fails in everything back to 7.0, which is the
oldest branch I have running. The error message varies a bit.
> varchar works, how come double does not?
The SQL spec has varchar, it does not have double.
<character string type> ::=
CHARACTER [ <left paren> <length> <right paren> ]
| CHAR [ <left paren> <length> <right paren> ]
| CHARACTER VARYING <left paren> <length> <right paren>
| CHAR VARYING <left paren> <length> <right paren>
| VARCHAR <left paren> <length> <right paren>
<approximate numeric type> ::=
FLOAT [ <left paren> <precision> <right paren> ]
| REAL
| DOUBLE PRECISION
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
