>
>> Considering that we are worried about someday having to adjust to a
>> SQL standard in this area, I think we ought to be as conservative as
>> possible about what we introduce as user-visible features here.
>> As an example, if they do go with "=>" as the parameter marker,
>> mixed notation would become a seriously bad idea because it would be
>> impossible to distinguish incidental use of => as an operator from
>> mixed notation.
>
I thing, so ANSI will be in conformance with Oracle - so I'll try to
check the possibility of the using => as any operator in Oracle
regards
Pavel Stehule
