Test Status
      JDBCRANDOMTEST
      (A) In the MySQL database mysql
      (B) In the MySQL database metadata
      (C) In the MySQL database metasql
      (D) In the MySQL database mysql
      (A) a
      (B) b
      (C) c
      (D) d
      (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) 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) Both Type 1 and Type 3
      (B) Both Type 1 and Type 2
      (C) Both Type 3 and Type 4
      (D) Type 4 only
      (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
      (A) Type 1
      (B) Type 2
      (C) Type 3
      (D) Type 4
      (A) Regular Statement
      (B) Interim Statement
      (C) Callable Statement
      (D) Prepared Statement
      (A) getNumberOfColumn
      (B) getMaxColumn
      (C) getColumnCount
      (D) getColumns
      (A) registerDriver() method
      (B) Class.forName()
      (C) Both A and B
      (D) getConnection()
      (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.