On Sunday 26 May 2002 17:58, Tom Lane wrote:
(...)
> If anyone does someday resurrect fjoin-like functionality, a reasonable
> SQL-style syntax for invoking it would be
>
> SELECT (bar(1)).*;
>
> which would still leave us wanting to raise an error if you just write
> "SELECT bar(1)".
The r
Joe Conway <[EMAIL PROTECTED]> writes:
> This is an illustration of why the expression SRF API isn't very useful
> for returning composite types ;)
> The number is actually a pointer to the result row. There is no way
> under the expression API to get at the individual columns directly.
You can
Ian Barwick wrote:
> but also this:
>
> func_test=# select bar(1);
> bar
> ---
> 139059784
> (1 row)
>
> What is this number? It often varies from query to query.
> Possibly an error-in-disguise because of something to do
> with the calling context?
This is an illustration of w
Using a recent build (22.5) from CVS, if I create a set returning
function in SQL like this:
func_test=# CREATE TABLE foo (id INT, txt1 TEXT, txt2 TEXT);
CREATE TABLE
func_test=# INSERT INTO foo VALUES(1, 'Hello','World');
INSERT 24819 1
func_test=#
func_test=# CREATE OR REPLACE FUNCTION bar(in
