How to distinguish serialization errors from others using pqxx

As I undersand, the only way to determine serialization errors is to parse
pqxx::sql_error exceptions' messages for keywords like "could not serialize"
etc.

Or am I wrong?

Thanks in advance
Saimon

--
View this message in context: http://postgresql.nabble.com/How-to-distinguish-serialization-errors-from-others-using-pqxx-tp5843145p5843271.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

Saimon <aimon.slim@gmail.com> wrote:

As I undersand, the only way to determine serialization errors is
to parse pqxx::sql_error exceptions' messages for keywords like
"could not serialize" etc.

I had to do a web search to find out what pqxx was. It is a C++
connector for PostgreSQL that's been around for ten years and most
recently released a new version two months ago.

http://pqxx.org/development/libpqxx/

From there it was pretty easy to find that making the SQLSTATE
available to the programmer is recognized as a desirable
enhancement, but has not yet been done:

http://pqxx.org/development/libpqxx/ticket/219

So I guess that leaves one parsing the text of the error messages
and hoping you know what language is going to be there.

Should pqxx be included in the table of externally maintained
client interfaces?:

http://www.postgresql.org/docs/current/static/external-interfaces.html

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general