java.sql.Statement interface
Derby Reference Manual
309
· All of the columns in the table
Note: If the java.sql.DatabaseMetaData.getBestRowIdentifier method does not find a
primary key, unique constraint, or unique index, the method must look for identifiers in all
of the columns in the table. When the method looks for identifiers this way, the method
will always find a set of columns that identify a row. However, a unique row might not be
identified if there are duplicate rows in the table.
java.sql.Statement interface
Derby does not implement the setEscapeProcessing method of java.sql.Statement. In
addition, the cancel method raises a "Feature not supported" exception.
The following table describes features of Statement methods that are specific to Derby.
Table 121.
Implementation notes on Statement methods
Returns
Signature
Implementation Notes
ResultSet
getGeneratedKeys()
If the user has indicated that
auto-generated keys should be
made available, this method
returns the same results as a call
to the
function. Otherwise this method
returns null.
boolean
execute(String sql, int []
columnIndexes)
Every column index in the
array must correlate to an
the target table of the INSERT.
Supported in embedded mode
only.
boolean
execute(String sql, String []
columnNames)
Every column name in the
array must designate an
the target table of the INSERT.
Supported in embedded mode
only.
int
executeUpdate(String sql, int []
columnIndexes)
Every column index in the
array must correlate to an
the target table of the INSERT.
Supported in embedded mode
only.
int
executeUpdate(String sql, String
[] columnNames)
Every column name in the
array must designate an
the target table of the INSERT.
Supported in embedded mode
only.
ResultSet objects
