Clob design flaw?

Topics: User Discussion
Jul 9, 2010 at 3:09 PM


Has anyone sucessfully used the type Oracle.DataAccess.Types.OracleClob as an output or return parameter?

For example,

  procedure get_clob_stuff (x out clob)

I call the stored procedure using ExecuteNonQuery() and when I try to get the value of the Clob, an exception is thrown
stating the connection is closed.

If I wrap the call with "Using New System.Transactions.TransactionScope()", the connection appears to remain open and I can get the value ...
seems like overkill though since there really is no transaction -- the transaction is just being used to fake out the database connection. 

Isn't starting a new distributed transaction pretty hefty?