Hi,

I'm currently assiting our development team with some additional logic that is housed in the database. The stored procedure has two "in" arguments. Once called, there are explicit dml operations associated with the "in" paramters. Currently, there is no need to return data - not even an "out status." The stored procedure is removing this explicit dml from the application layer to offload performance hits with large dml operations.

What I was curious to seek advice on is this - there is no need to return a ref cursor or any data set from the oracle object. Is there a way to invoke the stored procedure (akin to a callableStatement) within Hibernate knowing that we will not be consuming a ref cursor? Our current design implies that everything called from Oracle must return data. I'm considering it a hack to return a "dummy" ref cursor all in the name of allowing the stored proc to be used. Is there separation of concern here? In other words...if we're using stored procedures, are we moving outside of the "intent" of having a persistence layer?

Any advice on this would be truly appreciated.

Abe Woodrum
Boulder, Colorado