True,
but it still allowed me to write queries that I do not know how to
express otherwise.
Am 20.09.10 01:58, schrieb Tom Lane:
> =?UTF-8?B?SmFubiBSw7ZkZXI=?= writes:
>> Ok I now know that it really seems to do what I expected. But I still
>> wonder what it does if I use two functions f() and g(
=?UTF-8?B?SmFubiBSw7ZkZXI=?= writes:
> Ok I now know that it really seems to do what I expected. But I still
> wonder what it does if I use two functions f() and g() that return a
> different number of rows.
You get the least common multiple of their periods. It's ugly, and the
lack of any very
Ok I now know that it really seems to do what I expected. But I still
wonder what it does if I use two functions f() and g() that return a
different number of rows.
I'm guessing a query such as
SELECT id, (f(id)).a, (g(id)).b when f returns 3 rows and g returns two
row would yield something like
Hi,
I have a question which does not seem to be covered in the
documentation: I have a function f(i) that returns a table with three
columns (a, b, c).
In the documentation
(http://www.postgresql.org/docs/8.4/interactive/xfunc-sql.html#XFUNC-SQL-FUNCTIONS-RETURNING-SET)
it says that (even though d
