Subject | Re: [Firebird-Architect] Exec. statement parameters |
---|---|
Author | Adriano dos Santos Fernandes |
Post date | 2007-12-14T13:08:08Z |
Adriano dos Santos Fernandes escreveu:
proc(1, x => 2);
I think this is not good. So our SET could be used as in UPDATE:
execute procedure proc(1, 2);
execute procedure proc(set x = 1, y = 2);
select * from proc(1, 2);
select * from proc(set x = 1, y = 2);
execute statement 'select 1 from t where a = ? and b = ?' (1, 2);
execute statement 'select 1 from t where a = :a and b = :b' (set a =
1, b = 2);
This will not allow mix of named/unnamed.
Adriano
> Alex Peshkov escreveu:Oracle allow mix of named and unnamed parameter:
>
>> On Friday 14 December 2007 15:47, Adriano dos Santos Fernandes wrote:
>> 1. param set to value
>> 2. set param to be value
>>
> Consistent with UPDATE...SET: set param = value
proc(1, x => 2);
I think this is not good. So our SET could be used as in UPDATE:
execute procedure proc(1, 2);
execute procedure proc(set x = 1, y = 2);
select * from proc(1, 2);
select * from proc(set x = 1, y = 2);
execute statement 'select 1 from t where a = ? and b = ?' (1, 2);
execute statement 'select 1 from t where a = :a and b = :b' (set a =
1, b = 2);
This will not allow mix of named/unnamed.
Adriano