Ann W. Harrison wrote:

> If we make it easier to add messages, the resistance to fixing ambiguous
> messages will go done. For now, it's just so much easier to use an
> imprecise but reasonably appropriate message that we can't fix the problem.

Like Jonathon, I find the error messages in Firebird to almost useless
when developing. The only way I found to reliably track down the more
esoteric problems was to disable entire blocks of trigger/SP code
(binary chop) until I found the offending code.

This costs in time and effort and has led me twice to consider a switch
to Postgres, simply to reduce development times and costs.

Even Oracle gets its line numbers wrong but at least it points you in
the right direction (kudos to the originaltor of 'oraerr') - in the
past 3+ months FB error messages have tended to be either spot on or
totally misleading.

Of course, half of the time, the problem may be how I am using Firebird
- i.e writing SP driven template engines etc :-)

Jacqui