This table captures information about statements which have been executed using RUNTIMESTATISTICS with XPLAIN style (see the RUNTIMESTATISTICS section in the Java DB Reference Manual for more information on how to configure this).
Each row in this table describes a single statement which has been captured. Depending on the precise configuration of the RUNTIMESTATISTICS and XPLAIN features, there may be additional rows in the other XPLAIN system tables with additional information; the STMT_ID and TIMING_ID columns in this table are used to join against those tables.
Rows in this table are added automatically when Derby has been configured appropriately. The rows remain in the table until you delete them or drop the table.
Tuning Java DB contains general information about how to use XPLAIN style and the XPLAIN database tables.
|STMT_ID||CHAR||36||false||A unique identifier for this particular captured statement.|
|STMT_NAME||VARCHAR||128||true||The name of the associated query or statement. This value is NULL if the user did not assign a name. I'm not sure how the user assigns a name to a statement, perhaps by calling Statement.setCursorName()?|
|STMT_TYPE||CHAR||6||false||A code indicating what type of statement this is: 'S'=SELECT, 'I'=INSERT, 'U'=UPDATE, 'D'=DELETE, 'C'=CALL, 'DDL'=Data Definition, such as CREATE TABLE, 'SA'=SELECT (Approximate), or blank, indicating the statement was a comment.|
|STMT_TEXT||VARCHAR||32672||false||The text of the statement.|
|JVM_ID||CHAR||30||false||A code indicating what version of the JVM was running when this statement was captured: '4'=J2SE_14 - JDK 1.4.0 or 1.4.1, '5'= J2SE_142 - JDK 1.4.2, '6'=J2SE_15 - JDK 1.5, '7'=J2SE_16 - JDK 1.6|
|OS_IDENTIFIER||CHAR||30||false||Contains information about the operating system which was being used when this statement was captured.|
|XPLAIN_MODE||CHAR||1||true||A code indicating the XPLAIN mode which was in use when this statement was captured: 'F'=FULL, 'O'=ONLY.|
|XPLAIN_TIME||TIMESTAMP||true||Contains the date and time when this statement was captured.|
|XPLAIN_THREAD_ID||CHAR||32||false||The JVM thread which was running when this statement was captured.|
|TRANSACTION_ID||CHAR||32||false||An internal identifier for the transaction which was active when this statement was captured.|
|SESSION_ID||CHAR||32||false||An internal identifier for the session which was active when this statement was captured.|
|DATABASE_NAME||VARCHAR||128||false||Contains the name of the database which was being used when this statement was captured.|
|DRDA_ID||CHAR||32||true||In a network environment, this column contains an internal identifier for the network connection which was active when this statement was captured. In an embedded environment, this column is null.|
|TIMING_ID||CHAR||36||true||This field will be NULL unless SYSCS_UTIL.SYSCS_SET_STATISTICS_TIMING has been called to enable statistics timing. If statistics timings are being captured, then this column will contain the ID of the row in SYSXPLAIN_STATEMENT_TIMINGS which record the statement timing for this statement.|