In gram.y
Typename: SimpleTypename opt_array_bounds
{
$$ = $1;
$$-arrayBounds = $2;
}
| SETOF SimpleTypename opt_array_bounds
{
$$ = $2;
$$-arrayBounds =
Teodor Sigaev [EMAIL PROTECTED] writes:
May I eliminate SETOF from Typename and leave it
only for RETURNS?
Why do you want to?
I think the reason it's in Typename is the assumption that in future
we would try to extend the applicability of SETOF, not restrict it.
For instance I can see
Why do you want to?
Just simplify.
For instance I can see reasons for wanting SETOF on a function's input
parameter (to pass it a whole table or select result in one call).
I see. But Typename is used for table's definition for example. I can't imagine
column setof text.
--
Teodor
Teodor Sigaev [EMAIL PROTECTED] writes:
Why do you want to?
Just simplify.
I think you'd just be moving the complexity somewhere else.
regards, tom lane
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner
On Wed, Oct 04, 2006 at 09:04:11PM +0400, Teodor Sigaev wrote:
Why do you want to?
Just simplify.
For instance I can see reasons for wanting SETOF on a function's
input parameter (to pass it a whole table or select result in one
call).
I see. But Typename is used for table's definition
