>> But @ is used to denote client parameters in ADO.NET. I think we need
>> opinions if this could cause problems.
>
> This will be really tricky for ADO.NET developers. Because you will
> not be able to recognize "my" params. in code.
>
> Also parsing param names in FBClient will be difficult (it's now a
> little bit weird, supporting '@name' syntax and then translationg it
> to '?').

I think engine could do a better job here. If we agree that engine alone
would support the @name, the :name and ? syntax, in this case all
components could drop their parameter parsing code and use API to obtain
needed information. This, however, I suspect, requires API change (e.g.
introducing new XSQLDA version).

Roman