| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | 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-26 20:43:34 |
| Message-ID: | Pine.LNX.4.44.0206261800560.838-100000@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane writes:
> IIRC, a function is only considered to be a cast function if it matches
> by name *and schema* with the target type. So if you, for example,
> make a function public.int4(something), it'll never be considered a
> cast function for pg_catalog.int4. I had some doubts about that rule
> when I put it in, but so far have not thought of an alternative I like
> better.
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.
--
Peter Eisentraut peter_e(at)gmx(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2002-06-26 20:44:32 | Re: Democracy and organisation : let's make a revolution |
| Previous Message | Josh Berkus | 2002-06-26 20:22:00 | Re: Democracy and organisation : let's make a |