From: | Rod Taylor <pg(at)rbt(dot)ca> |
---|---|
To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
Cc: | Tony Caduto <tony_caduto(at)amsoftwaredesign(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Did this work in earlier version of Postgres? |
Date: | 2006-03-24 00:26:15 |
Message-ID: | 1143159975.79972.137.camel@home |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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.
--
From | Date | Subject | |
---|---|---|---|
Next Message | Joel Miller | 2006-03-24 00:30:10 | Re: [SUGGESTION] CVSync |
Previous Message | Joel Miller | 2006-03-24 00:21:34 | Re: [SUGGESTION] CVSync |