Dmitry Yemanov wrote:
> LacaK wrote:
>> 1. SELECT ... INTO ... FROM ...
>> SQL:2003 (INTO is before FROM):
>> SELECT [ <set quantifier> ] <select list>
>> INTO <select target list>
>> <table expression>
>> select f into :v from t;
>> FB (INTO AFTER SELECT, does not allow into before from):
>> select f from t into :v ;
>> I know, it is only detail, because it does not affect functionality, ...
>> consider please if it is interesting for you or not
> Tracker is awaiting you :-)
>> 2. UPDATE <multiple column assignment>
>> Are there plans or intention extent UPDATE statement to :
>> UPDATE <table>
>> SET ( col1 ,col2 ) = (val1,val2) | ROW (val1[,val2]) | (<query expression>)
> This is a generic feature (row value constructors) that has nothing to
> do with UPDATE. Consider also WHERE (fld1, fld2) = (1, 2) etc. Almost
> everything in the syntax should be extended.
Yes, you are right.
But I guess, that best usability is in update statement.
(When I need update totals in master table using values from detail
table ... at least update is only statement, where I encounter lack of
I guess, that in select statement you can often rewirite it using for
I do not know, how much of your work is required to implement "row value
constructor". If it is too dificult task and you think, that it is not
interstnig feature, then I will not add such request to tracker.
If you think, that it is useful feature I will add ticket ...