"Pavel Stehule" <[EMAIL PROTECTED]> writes:
x, y := r;
>
>>> That strikes me as a really bad idea. It weakens both syntax and
>>> semantic error checking, to accomplish how much?
>>
>> Could use PHP-style thingy:
>> LIST(x, y) := r;
Actually, ROW(x, y) would be the right spelling per SQL c
"Pavel Stehule" <[EMAIL PROTECTED]> writes:
x, y := r;
>
>>> That strikes me as a really bad idea. It weakens both syntax and
>>> semantic error checking, to accomplish how much?
>>
>> Could use PHP-style thingy:
>> LIST(x, y) := r;
Actually, ROW(x, y) would be the right spelling per SQL c
x, y := r;
That strikes me as a really bad idea. It weakens both syntax and
semantic error checking, to accomplish how much?
Could use PHP-style thingy:
LIST(x, y) := r;
Chris
It's inconsystency :-(.
EXECUTE INTO and SELECT INTO use scalar of vectors without anything.
Pavel
___
Tom Lane said:
> "Pavel Stehule" <[EMAIL PROTECTED]> writes:
>> x, y := r;
>
> That strikes me as a really bad idea. It weakens both syntax and
> semantic error checking, to accomplish how much?
>
Where does the idea come from anyway? Has it been discussed on -hackers? I
don't recall seein
"Pavel Stehule" <[EMAIL PROTECTED]> writes:
> x, y := r;
That strikes me as a really bad idea. It weakens both syntax and
semantic error checking, to accomplish how much?
It's same as select into or execute into (using same code). And behave is
like row variable := row variable. I am
