At 11:27 PM 12/09/2002 -0400, Tom Lane wrote: >You mean hardwire the names "plpgsql_language_handler", etc, as being >ones that should return such-and-such instead of OPAQUE?
No; I actually mean modifying the function definition macros (PG_FUNCTION_INFO etc) to allow function definitions to (optionally) include return type (at least for builtin types with fixed IDs) - they already define the invocation method etc, so it does not seem a big stretch to add a return type ID. Not all functions would need to use these, but when a user defines a function they could be checked. And in the case of the plpgsql handlers, they would of course be defined. ---------------------------------------------------------------- Philip Warner | __---_____ Albatross Consulting Pty. Ltd. |----/ - \ (A.B.N. 75 008 659 498) | /(@) ______---_ Tel: (+61) 0500 83 82 81 | _________ \ Fax: (+61) 0500 83 82 82 | ___________ | Http://www.rhyme.com.au | / \| | --________-- PGP key available upon request, | / and from pgp5.ai.mit.edu:11371 |/ ---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
