I can imagine this will cause some people headaches, but I can't imagine
it would cause more pain than the schema support changes are going to
cause. I would much prefer having to do something like:
find / -type f -print | xargs perl -pe 's/ExecAppend/ExecInsert/g'
rather than digging through client code to make query changes. I can
definitely see the benefits from an ease of use side, was there
something else that prompted the change?
Robert Treat
On Sun, 2002-07-07 at 23:56, Bruce Momjian wrote:
> There is discussion on hackers to change certain error message text for
> 7.3. The change would be:
>
> ERROR: ExecAppend: ... => ERROR: ExecInsert: ...
>
> and
>
> ERROR: ExecReplace: ... => ERROR: ExecUpdate: ...
>
>
> APPEND/REPLACE are the old QUEL-language commands, while INSERT/UPDATE
> are the SQL ones.
>
> Does such a change in 7.3 cause anyone problems? We are particularly
> interested in people who parse these error strings and don't want them
> to change.
>
> --
> Bruce Momjian | http://candle.pha.pa.us