Fabricio Araujo wrote:

> Helen,
> I think that the original subject means that we would
> *also* have named parameters. If you ever worked
> with MSSQL Server, you know of this
>

Exactly.

> create procedure X1
> @p1 int,
> @p2 int
> as
> go
>
> you can call the proc as
>
> exec X1
> @p2 = 1,
> @p1 = 2
>
> or
>
> exec X1
> @p1 = 2,
> @p2 = 1
>
>
>
> or
>
> exec X1 2,1
>
>
> So using of named parameters, in conjunction with
> default parameters give high mantainability (save the
> DBA of a lot hassles when the time to expand the
> procs without breaking calling code).
>

And like as INSERT, UPDATE and SELECT you don't need to care about order of fields/parameters.

Nothing need to change in the API. It don't break access layers.
Small changes are required in the parser and possibly in pass1.


Adriano