Re: [Firebird-devel] Parameterized Exceptions

[Adriano d. S. F. <adr...@gm...>]

Vlad Khorsun wrote:
>> Currently user can't create good exception texts and rely on them,
>> because exceptions generally need more informations. So user need to
>> throw exceptions passing its complete text [exception e1 'Exception ' ||
>> info1 || ' at ' || info2]. This lose the ability to create exception
>> texts and to catch the parameters without parse the formated text.
>>
>> The exceptions are currently encoded in this way:
>> isc_except, <number>,
>> isc_random, <string>
>>
>> I propose to make parameters directly inside user text exceptions, like
>> this:
>> create exception e1 'Exception @1 at @2';
>>
>> This is easy for user, easy for the engine. Does not need metadata
>> extensions and is backward compatible.
> 
>     Why not implement built-in FORMAT function instead ?
> 
This does not allow the client (or even in PSQL) to catch the exception
parameters, and to define messages right in the exception. FORMAT is
useful, and should format the same way exceptions are formated, but does
not substitute it.


Adriano