| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "Eduardo Stern" <eduardo(at)stern(dot)com(dot)br>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Cast and Schemas don't work as expected |
| Date: | 2003-01-24 01:57:27 |
| Message-ID: | GNELIHDDFBOCMGBFGEFOIECOCFAA.chriskl@familyhealth.com.au |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
That's probably because CASTS are database-wide and are not in schemas.
Chris
> -----Original Message-----
> From: pgsql-hackers-owner(at)postgresql(dot)org
> [mailto:pgsql-hackers-owner(at)postgresql(dot)org]On Behalf Of Eduardo Stern
> Sent: Sunday, 19 January 2003 11:07 PM
> To: pgsql-hackers(at)postgresql(dot)org
> Subject: [HACKERS] Cast and Schemas don't work as expected
>
>
> The CREATE CAST command is't supporting schemas on the type parameters.
>
> A query such as:
>
> CREATE CAST (public.lo AS oid) WITH FUNCTION newoid (public.lo)
> AS IMPLICIT;
>
> Gives an error. And the problem happens when you create a CAST without the
> schema notation, and then try to do a dump/restore cycle.
>
>
> []s
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rod Taylor | 2003-01-24 03:29:00 | Re: New buildin function |
| Previous Message | Marc G. Fournier | 2003-01-24 00:58:55 | Re: Release Scheduales: 7.2.4 & 7.3.2 |