Home >> All >> org >> apache >> derby >> iapi >> sql >> [ execute Javadoc ]

• org.apache.derby.iapi.sql.execute: Javadoc index of package org.apache.derby.iapi.sql.execute.


Package Samples:

• org.apache.derby.iapi.sql.execute

Classes:

• ExecAggregator: An ExecAggregator is the interface that execution uses to an aggregate. System defined aggregates will implement this directly. The life time of an ExecAggregator is as follows. An ExecAggregator instance is created using the defined class name. Its setup() method is called to define its role (COUNT(*), SUM, etc.). Its newAggregator() method may be called any number of times to create new working aggregators as required. These aggregators have the same role and must be created in an initialized state. accumlate and merge will be called across these set of aggregators One of these aggregators will ...
• RunTimeStatistics: A RunTimeStatistics object is a representation of the query execution plan and run time statistics for a java.sql.ResultSet. A query execution plan is a tree of execution nodes. There are a number of possible node types. Statistics are accumulated during execution at each node. The types of statistics include the amount of time spent in specific operations (if STATISTICS TIMING is SET ON), the number of rows passed to the node by its child(ren) and the number of rows returned by the node to its parent. (The exact statistics are specific to each node type.) RunTimeStatistics is most meaningful for ...
• ExecutionStmtValidator: An ExecutionStatementValidator is an object that is handed a ConstantAction and asked whether it is ok for this result set to execute. When something like a trigger is executing, one of these gets pushed. Before execution, each validator that has been pushed is invoked on the result set that we are about to execution. It is up to the validator to look at the result set and either complain (throw an exception) or let it through.
• ExecutionFactory: This is the factory for creating a factories needed by execution per connection, and the context to hold them. There is expected to be one of these configured per database. If a factory is needed outside of execution (say, data dictionary or compilation), then it belongs in the LanguageConnectionContext.
• ResultSetFactory: ResultSetFactory provides a wrapper around all of the result sets needed in an execution implementation. For the activations to avoid searching for this module in their execute methods, the base activation supertype should implement a method that does the lookup and salts away this factory for the activation to use as it needs it.
• ConstantAction: This interface describes actions that are ALWAYS performed for a Statement at Execution time. For instance, it is used for DDL statements to describe what they should stuff into the catalogs. An object satisfying this interface is put into the PreparedStatement and run at Execution time.
• NoPutResultSet: The NoPutResultSet interface is used to provide additional operations on result sets that can be used in returning rows up a ResultSet tree. Since the ResulSet operations must also be supported by NoPutResultSets, we extend that interface here as well.
• TemporaryRowHolder: This is a class that is used to temporarily (non-persistently) hold rows that are used in language execution. It will store them in an array, or a temporary conglomerate, depending on the number of rows. It is used for deferred DML processing.
• CursorResultSet: The CursorResultSet interface is used to provide additional operations on result sets that can be used in cursors. Since the ResulSet operations must also be supported by cursor result sets, we extend that interface here as well.
• TargetResultSet: The TargetResultSet interface is used to provide additional operations on result sets that are the target of a bulk insert or update. This is useful because bulk insert is upside down - the insert is done via the store.
• ExecRow: Execution sees this extension of Row that provides connectivity to the Storage row interface and additional methods for manipulating Rows in execution's ResultSets.
• ExecutionContext: ExecutionContext stores the factories that are to be used by the current connection. It also provides execution services for statement atomicity.
• ResultSetStatisticsFactory: ResultSetStatisticsFactory provides a wrapper around all of the result sets statistics objects needed in building the run time statistics.
• ExecPreparedStatement: Execution extends prepared statement to add methods it needs for execution purposes (that should not be on the Database API).
• ScanQualifier: ScanQualifier provides additional methods for the Language layer on top of Qualifier.
• ExecCursorTableReference: This is a table name reference that can be retrieved from an active cursor.
• RowChanger: Perform row at a time DML operations of tables and maintain indexes.
• ExecIndexRow: This is an extension of ExecRow for use with indexes and sorting.
• CursorActivation: CursorActivation includes an additional method used on cursors.
• TupleFilter: A TupleFilter is used to qualify rows from a tuple stream.

Home | Contact Us | Privacy Policy | Terms of Service