[Libpqxx-general] Transaction status

[Maxime van Noppen]

On 07/12/09 09:07, Jeroen T. Vermeulen wrote:
> There's a smell of danger to this.  The workings of transaction status
> isn't always completely obvious, so I'm worried that more people will
> shoot themselves in the foot with it than will get real use from it.  It
> gets worse if the state machine ever needs changing (maybe for a 2pc
> implementation or something).

> But before we get to that, I'd be interested to know a bit more about what
> you're trying to do, so that I can see if there is really a sufficient
> argument to rely on data flow instead of control flow in the first place.

In fact I fully agree with you and I misused the library and had a weird
code structure. Having that reworked I can now track the transaction
status via the exceptions and avoid usage_errors.

Thanks ! :)

-- 
Maxime