Diff of /incubator/derby/code/trunk/java/client/org/apache/derby/client/net/StatementRequestInterface.java
Parent Directory
| 
Revision Log
| 
Patch
--- incubator/derby/code/trunk/java/client/org/apache/derby/client/net/StatementRequestInterface.java 2005/05/02 05:18:08 165584
+++ incubator/derby/code/trunk/java/client/org/apache/derby/client/net/StatementRequestInterface.java 2005/05/02 06:25:59 165585
@@ -20,72 +20,72 @@
package org.apache.derby.client.net;
-import org.apache.derby.client.am.SqlException;
-import org.apache.derby.client.am.Section;
import org.apache.derby.client.am.ColumnMetaData;
+import org.apache.derby.client.am.Section;
+import org.apache.derby.client.am.SqlException;
// In general, all required data is passed.
// In addition, Material Statement objects are passed for convenient access to any material statement caches.
// Implementations of this interface should not dereference common layer Statement state, as it is passed in,
// but may dereference material layer Statement state if necessary for performance.
-public interface StatementRequestInterface
-{
- public void writeExecuteImmediate (NetStatement materialStatement,
- String sql,
- Section section) throws SqlException;
-
- public void writePrepareDescribeOutput (NetStatement materialStatement,
- String sql,
- Section section) throws SqlException;
-
- public void writePrepare (NetStatement materialStatement,
- String sql,
- Section section) throws SqlException;
-
- public void writeOpenQuery (NetStatement materialStatement,
- Section section,
- int fetchSize,
- int resultSetType) throws SqlException;
-
- public void writeExecute (NetPreparedStatement materialPreparedStatement,
- Section section,
- org.apache.derby.client.am.ColumnMetaData parameterMetaData,
- Object[] inputs,
- int numInputColumns,
- boolean outputExpected,
- // This is a hint to the material layer that more write commands will follow.
- // It is ignored by the driver in all cases except when blob data is written,
- // in which case this boolean is used to optimize the implementation.
- // Otherwise we wouldn't be able to chain after blob data is sent.
- // If we could always chain a no-op DDM after every execute that writes blobs
- // then we could just always set the chaining flag to on for blob send data
- boolean chainedWritesFollowingSetLob) throws SqlException;
-
-
- public void writeOpenQuery (NetPreparedStatement materialPreparedStatement,
- Section section,
- int fetchSize,
- int resultSetType,
- int numInputColumns,
- ColumnMetaData parameterMetaData,
- Object[] inputs) throws SqlException;
-
- public void writeDescribeInput (NetPreparedStatement materialPreparedStatement,
- Section section) throws SqlException;
-
- public void writeDescribeOutput (NetPreparedStatement materialPreparedStatement,
- Section section) throws SqlException;
-
- public void writeExecuteCall (NetStatement materialStatement,
- boolean outputExpected,
- String procedureName,
- Section section,
- int fetchSize,
- boolean suppressResultSets, // set to true for batched calls
- int resultSetType,
- ColumnMetaData parameterMetaData,
- Object[] inputs) throws SqlException;
+
+public interface StatementRequestInterface {
+ public void writeExecuteImmediate(NetStatement materialStatement,
+ String sql,
+ Section section) throws SqlException;
+
+ public void writePrepareDescribeOutput(NetStatement materialStatement,
+ String sql,
+ Section section) throws SqlException;
+
+ public void writePrepare(NetStatement materialStatement,
+ String sql,
+ Section section) throws SqlException;
+
+ public void writeOpenQuery(NetStatement materialStatement,
+ Section section,
+ int fetchSize,
+ int resultSetType) throws SqlException;
+
+ public void writeExecute(NetPreparedStatement materialPreparedStatement,
+ Section section,
+ org.apache.derby.client.am.ColumnMetaData parameterMetaData,
+ Object[] inputs,
+ int numInputColumns,
+ boolean outputExpected,
+ // This is a hint to the material layer that more write commands will follow.
+ // It is ignored by the driver in all cases except when blob data is written,
+ // in which case this boolean is used to optimize the implementation.
+ // Otherwise we wouldn't be able to chain after blob data is sent.
+ // If we could always chain a no-op DDM after every execute that writes blobs
+ // then we could just always set the chaining flag to on for blob send data
+ boolean chainedWritesFollowingSetLob) throws SqlException;
+
+
+ public void writeOpenQuery(NetPreparedStatement materialPreparedStatement,
+ Section section,
+ int fetchSize,
+ int resultSetType,
+ int numInputColumns,
+ ColumnMetaData parameterMetaData,
+ Object[] inputs) throws SqlException;
+
+ public void writeDescribeInput(NetPreparedStatement materialPreparedStatement,
+ Section section) throws SqlException;
+
+ public void writeDescribeOutput(NetPreparedStatement materialPreparedStatement,
+ Section section) throws SqlException;
+
+ public void writeExecuteCall(NetStatement materialStatement,
+ boolean outputExpected,
+ String procedureName,
+ Section section,
+ int fetchSize,
+ boolean suppressResultSets, // set to true for batched calls
+ int resultSetType,
+ ColumnMetaData parameterMetaData,
+ Object[] inputs) throws SqlException;
- public void writeSetSpecialRegister (java.util.ArrayList sqlsttList) throws SqlException;
+ public void writeSetSpecialRegister(java.util.ArrayList sqlsttList) throws SqlException;
}
