> Reason of this problem is that PsqlODBC handles the large object
without
> transaction. Since PostgreSQL 6.5, the large object must be handled
in
> transaction.
>
> To solve, we should insert source code to begin transaction into
PsqlODBC
> source before calling lo_create and lo_open functions. Also should
commit
> transaction after calling lo_close too.
What is the possible side effects of not committing after lo_close? I'm
just wondering, incase I have to do anything to the JDBC driver's lo
support.
Whilst on the subject, what is the prospect of nested transactions for
7.0? My number 1 question I get asked is caused by having to use
transactions for lo's, and it would be nice to wrap the JDBC standard lo
calls in their own transactions, but if autoCommit is false (ie, already
in a transaction), then this is a problem.
Nestable transactions (even only 1 extra level) would solve this
problem.
Peter
--
Peter Mount
Enterprise Support
Maidstone Borough Council
Any views stated are my own, and not those of Maidstone Borough Council.