Test Status
      (A) A Type 3 driver is a JDBC-Net pure Java driver
      (B) This translates JDBC calls into a database -dependent net protocol.
      (C) Vendors of database middleware products can implement this type of driver into their products to provide interoperability with the greatest number of database servers.
      (D) a,b
      (A) One
      (B) Two
      (C) Three
      (D) Four
      (A) Both types of result sets will make changes visible if they are closed and then reopened.
      (B) A result set that is TYPE_SCROLL_INSENSITIVE does not reflect changes made while it is still open and one that is TYPE_SCROLL_SENSITIVE does.
      (C) You will get a scrollable ResultSet object if you specify one of these ResultSet constants.
      (D) A result set that is TYPE_SCROLL_INSENSITIVE makes the result set read only while one that is TYPE_SCROLL_SENSITIVE does not.
      (A) UNIQUE
      (C) SEQUENCE
      (D) None of the above -- Surrogate keys are not implemented in MySQL.
      (A) Type 4 driver is "native protocol, pure java" driver
      (B) Type 4 drivers can not be used with Netscape
      (C) Type 4 drivers are 100% Java compatible
      (D) Type 4 drivers uses Socket class to connect to the database
      (A) When a connection is created, it is in auto-commit mode.
      (B) If the value is true each individual SQL statement is treated as a transaction and will be automatically committed right after it is executed.
      (C) once auto-commit mode is disabled, no SQL statements will be committed until you call the method commit explicitly
      (D) By default the JDBC call is in auto-commit mode.
      (A) CallableStatement clbstmnt = con.prepareCall("{call totalStock}");cs.executeQuery();
      (B) Statement stmt = connection.createStatement();stmt.execute("totalStock()");
      (C) StoreProcedureStatement spstmt = connection.createStoreProcedure("totalStock()");spstmt.executeQuery();
      (D) PrepareStatement pstmt = connection.prepareStatement("totalStock()");pstmt.execute();
      (A) Native-protocol, pure Java driver
      (B) JDBC-Net, pure Java driver
      (C) Native-API, partly Java driver
      (D) JDBC-ODBC Bridge plus ODBC driver
      (A) Regular Statement
      (B) Interim Statement
      (C) Callable Statement
      (D) Prepared Statement
      (A) A workaround is to explicitly call the method DriverManager.registerDriver(new YourDriverClass).
      (B) The problem is due to race condition in the class loader.
      (C) The race condition prevents the static section of code in the driver class from executing and registering the driver with the DriverManager.
      (D) All the above.
      (A) Type 4
      (B) Type 3
      (C) Type 2
      (D) Type 1
      (A) Type 1 only
      (B) Type 2 only
      (C) Both Type 3 and Type 4
      (D) All of Type 1, Type 2, Type 3 and Type 4
      (A) This problem can be caused by running a JDBC applet in a browser that supports the JDK 1.0.2, such as Netscape Navigator 3.0. The JDK 1.0.2 does not contain the JDBC API, so the DriverManager class typically isn't found by the Java virtual machine running
      (B) Most of the browsers cannot download java.* because of security reasons. Hence many vendors of all-Java JDBC drivers supply versions of the java.sql.* classes that have been renamed to jdbc.sql.*, along with a version of their driver that uses these modify
      (C) Add import jdbc.sql.* in your applet code instead of java.sql.*, and add the jdbc.sql.* classes provided by your JDBC driver vendor to your applet's codebase, then all of the JDBC classes needed by the applet can be downloaded by the browser at run time,
      (D) All of the above