From: | Hannu Krosing <hannu(at)tm(dot)ee> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Thomas Lockhart <lockhart(at)fourpalms(dot)org>, PostgreSQL Hackers List <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: SQL99, CREATE CAST, and initdb |
Date: | 2002-06-27 12:31:34 |
Message-ID: | 1025181094.25880.137.camel@taru.tm.ee |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, 2002-06-27 at 02:10, Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > Perhaps it wouldn't be such a terrible idea after all to store the casting
> > paths separately, such as in a system table pg_cast (from, to, func,
> > implicit). This would implement the SQL99 spec fairly exactly.
>
> Well, maybe. One question is how that would fit in with schemas.
> Thomas appears to want your schema search path to have some effect on
> which casts you can see --- which I'm not at all sure I agree with,
I hope that schema search path has some effect on other user-defined
stuff like simple functions and operators.
> but if that's the requirement then the above doesn't do it either.
What is and what is not affected by schemas ?
Are the docs on our schema usage already available someplace ?
-------------
Hannu
From | Date | Subject | |
---|---|---|---|
Next Message | Rod Taylor | 2002-06-27 12:34:22 | Re: Postgres idea list |
Previous Message | Marc G. Fournier | 2002-06-27 12:28:25 | Re: Postgres idea list |