| From: | "Hiroshi Saito" <saito(at)inetrt(dot)skcapi(dot)co(dot)jp> |
|---|---|
| To: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
| Cc: | "Andreas Pflug" <Andreas(dot)Pflug(at)web(dot)de>, <pgadmin-hackers(at)postgresql(dot)org> |
| Subject: | binary-compatible of pgCast |
| Date: | 2003-09-09 02:49:14 |
| Message-ID: | 022f01c3767c$f4d2e4f0$1f324d80@w2k |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
Hi Dave.
I have one cast of binary-compatible for largeobject.
Though it is hardly made except for it,
it thinks that we must show the policy of it.
This is made by psql.
CREATE CAST (lo AS integer) WITHOUT FUNCTION;
It doesn't appear on pgadmin for the limitation.
But, though it is binary-compatible,
Cast of the next which is supposed to be restricted can be made by Dialog.
CREATE CAST (timestamp AS int8) WITHOUT FUNCTION AS EXPLICIT;
This shouldn't be made if it is here because it is restricted.
I want to handle this as an effective thing.
It can be handled with this patch.
Any Comment?
Regards,
Hiroshi Saito
| Attachment | Content-Type | Size |
|---|---|---|
| pgCast_patch | application/octet-stream | 1.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hiroshi Saito | 2003-09-09 05:17:13 | pgAggregate problem any function |
| Previous Message | Dave Page | 2003-09-08 19:12:08 | Re: frmMain_patch |