From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | wieck(at)debis(dot)com (Jan Wieck) |
Cc: | peter_e(at)gmx(dot)net, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] update_pg_pwd |
Date: | 1999-12-13 16:02:41 |
Message-ID: | 11814.945100961@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
wieck(at)debis(dot)com (Jan Wieck) writes:
> One last point though. The comment says it's using lower case
> name now to be callable from SQL, what it isn't because of
> it's Opaque return type in pg_proc.
> pgsql=> select update_pg_pwd();
> ERROR: typeidTypeRelid: Invalid type - oid = 0
> Is that a wanted (needed) capability or should I better
> change the comment to reflect it's real nature?
What would you expect the SELECT to produce here? I think the error
message is pretty poor, but I can't really see OPAQUE functions being
allowed in expression contexts...
I don't really like the description of these functions as returning
something "OPAQUE", anyway, particularly when that is already being
(mis) used for user-defined type input/output functions. I wish
they were declared as returning something like "TUPLE".
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 1999-12-13 16:11:50 | Re: [HACKERS] Datatype MONEY |
Previous Message | Tom Lane | 1999-12-13 15:46:04 | Re: [HACKERS] update_pg_pwd |