Michael Van Canneyt wrote:
Regarding the content of your question in the bug: AFAIU it's for
backward compatibility. The generic db error shows the error message.
The specialized PostgreSQL error does the same, but also shows it in
detail (perhaps, can't remember, there can be a list of multiple errors).
I'm sure the guy who implemented this (I think Ludo Brands) can tell you
exactly what's going on.
I have changed it, but added an option so you can ask all information as
it was.
Name of option please: is it a global or associated with the connection
object?
Note that all parts of the error are always available as fields in the
exception class.
--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk
[Opinions above are the author's, not those of his employers or colleagues]
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
