On Thu, 2006-03-23 at 16:05 -0800, Joshua D. Drake wrote: > Rod Taylor wrote: > > On Thu, 2006-03-23 at 17:31 -0600, Tony Caduto wrote: > >> 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. > > > > CREATE DOMAIN double AS float8; > > > > There, now the type exists ;) > > That's a little too perl for me ;)
I suppose it depends on the goal. If it is an application that is to be supported on more than one database, defining types and other things for a given DB type (PostgreSQL) is easier than injecting a large number of SWITCH statements into the code. -- ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings