How can I determine whether a Statement and its ResultSet will be closed on a commit or rollback?
Location: http://www.jguru.com/faq/view.jsp?EID=391306 Created: Mar 30, 2001 Author: Joe Sam Shirah (http://www.jguru.com/guru/viewbio.jsp?EID=42100) Use the DatabaseMetaData methods supportsOpenStatementsAcrossCommit() and supportsOpenStatementsAcrossRollback(). More.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.
Related Questions
With NHibernate and Transaction do I rollback on commit failure or does it auto rollback on single commit?
Java JDBC ResultSet metadata FAQ: How do I dynamically determine the number of columns in a Java/JDBC ResultSet?
How can I take a function out of a commit/rollback process without modifying the logic in the calling COMMIT SYS Parent function?
I've requested an updatable ResultSet and my driver supports them, but I still don't get an updatable ResultSet. Why?
Why am I getting an "ORA-01000: maximum open cursors exceeded" error, even though I closed all ResultSet, Statement, and Connection objects?
Is it a better practice to explicitly call transaction rollback or let an exception trigger an implicit rollback?