Darrell Rials

Tim Holloway wrote:And, while I don't myself consider continuous-integration systems such as Jenkins to be DevOps, strictly speaking, that's another tool that it's good to know how to tweak so that when it does its thing, the results will be more DevOps-friendly.

I'm in the same situation as the original poster. Anyone care to define "DevOps-friendly"?

Shane Lee wrote:Hi Unu ,
Ha thats a while back since i worked on that! Looked at my existing code that i have on my laptop and this is a code snippet of how i called a stored procedure.

private static final String mappingTemplateItem = "begin ? := iGET_TEMPLATE_ITEM(?,?); end;"; private CallableStatement cs = null; private ResultSet result = null; cs = (CallableStatement)conn.prepareCall(mappingTemplateItem); // register the type of the out param - an Oracle specific type cs.registerOutParameter(1, OracleTypes.CURSOR); cs.setString(2, mappingTemplate.getMappingTemplateCode()); cs.setString(3, templateType); cs.execute(); //result = ((OracleCallableStatement)cs).getCursor(1); result = (ResultSet) cs.getObject(1);

As you can see from the above comment, i use java.sql.CallableStatement now instead of OracleCallableStatement.

Brilliant! Not only can I avoid using yet another Oracle-specific type, the code is cleaner and easier to understand. I was looking at some rather nasty changes to setting up the connection pool, which I had no assurance would work. Now if we could only get Oracle to (a) change their documentation on how to use a Cursor, and (b) allow returning pure result sets instead of having to return a cursor object.