On Wed, Jun 29, 2011 at 11:41 AM, Jeff Davis <pgsql(at)j-davis(dot)com> wrote:
> Robert didn't really seem to like the idea of throwing an error though
> -- Robert, can you expand on your reasoning here?
I guess I don't have any terribly well-thought out reasoning - maybe
it's fine. It just seems strange to have a type that you can't
But now that I'm thinking about this a little more, I'm worried about this case:
CREATE TABLE foo AS RANGE('something'::funkytype, 'somethingelse'::funktype);
DROP TYPE funkytype;
It seems to me that the first statement had better fail, or else the
second one is going to create a hopeless mess (imagine that a new type
comes along and gets the OID of funkytype).
It also seems a bit strange to me that we're contemplating a system
where users are always going to have to cast the return type.
Generally, casts are annoying and we want to minimize the need for
them. I'm not sure what the alternative is, though, unless we create
separate constructor functions for each type: int8range_cc(1, 2).
The Enterprise PostgreSQL Company
In response to
pgsql-hackers by date
|Next:||From: Josh Berkus||Date: 2011-06-29 16:34:54|
|Subject: Re: Inconsistency between postgresql.conf and docs|
|Previous:||From: Merlin Moncure||Date: 2011-06-29 16:15:17|
|Subject: Re: patch: Allow \dd to show constraint comments|