Tag: programming languages

O (a) Type 1 driver

O (b) Type 2 driver

O (c) Type 3 driver

O (d) Type 4 driver

O (a) PreparedStatement

O (b) ParameterizedStatement

O (c) ParameterizedStatement and CallableStatement

O (d) All kinds of Statements (i.e. which implement a sub interface of Statement)

O (a) By invoking the method get (..., String type) on the ResultSet, where type is the database

O (b) By invoking the method get (..., Type type) on the ResultSet, where Type is an object

O (c) By invoking the method getValue (...), and cast the result to the desired java type.

O (d) By invoking the special getter methods on the ResultSet: getString (...), get Boolean (...),

O (a) By making use of the InsertStatement, DeleteStatement or UpdateStatement classes

O (b) By invoking the execute(...) or executeUpdate(...) method of a normal Statement object

O (c) By invoking the executeInsert(...), executeDelete(...) or executeUpdate(...) methods of

O (d) By making use of the execute(...) statement of the DataModificationStatement object

O (a) You must catch the checked SQLException which is thrown by the method which executes

O (b) You must catch the unchecked SQLWarningException which is thrown by the method

O (c) You must invoke the getWarnings() method on the Statement object (or a sub interface

O (d) You must query the ResultSet object about possible warnings generated by the database

O (a) A DataSource is the basic service for managing a set of JDBC drivers

O (b) A DataSource is the Java representation of a physical data source

O (c) A DataSource is a registry point for JNDI-services

O (d) A DataSource is a factory of connections to a physical data source

O (a) This means that the ResultSet is insensitive to scrolling

O (b) This means that the Resultset is sensitive to scrolling, but insensitive to updates, i.e. not

O (c) This means that the ResultSet is sensitive to scrolling, but insensitive to changes made

O (d) The meaning depends on the type of data source, and the type and version of the driver

O (a) Yes, but only if you call the method openCursor() on the ResultSet, and if the driver and

O (b) Yes, but only if you indicate a concurrency strategy when executing the statement, and

O (c) Yes, but only if the ResultSet is an object of class UpdateableResultSet, and if the driver

O (d) No, ResultSets are never updateable. You must explicitly execute DML statements (i.e.

[_] [a] A transaction is a set of successfully executed statements in the database

[_] [b] A transaction is finished when commit() or rollback() is called on the Connection object,

[_] [c] A transaction is finished when commit() or rollback() is called on the Transaction object

[_] [d] A transaction is finished when close() is called on the Connection object.

O (a) By asking a Transaction object to your Connection, and calling the method begin() on it

O (b) By asking a Transaction object to your Connection, and setting the autoCommit property

O (c) By calling the method beginTransaction() on the Connection object

O (d) By setting the autoCommit property of the Connection to false, and execute a statement