I had previously asked about running stored procedures within the same
transaction as other write operations and was advised to use a
TransactionDelegate:
http://www.objectstyle.org/cayenne/lists/cayenne-user/2005/07/0132.html
I'm fairly certain it wasn't doing this before, but in one of the
recent milestones, it started spawning a new connection for the
queries run within the willCommit() method.
While a rollback triggered by my "inner" connection would trigger a
rollback in the "outside" connection, the locking is all screwed up...
write locks are still held on tables needed by the stored procedure,
so it deadlocks now. I poked around some of the new Transaction stuff,
but I can't seem to figure out how I might force a ProcedureQuery to
be appended to the same *database* transaction, not just Cayenne
transaction.
Cris
This archive was generated by hypermail 2.0.0 : Mon Feb 06 2006 - 09:51:55 EST