click below
click below
Normal Size Small Size show me how
OCPJP709.6
Cert Obj Use PreparedStatement and CallableStatement Objects
[9.6.1]PreparedStatement | PreparedStatement can improve the performance of a frequently executed query because the SQL part of the statement is precompiled in the database. |
[9.6.2] CallableStatement | CallableStatement is used to execute a named stored procedure or function.Unlike prepared statements, stored procedures and functions must exist before a CallableStatement can be executed on them.The stored procedure may or may not return results |
[9.6.3]Named programs,named, compiled and stored in the database | There are three types of these small programs: procedures, functions, and triggers. |
[9.6.4]executeQuery() does not take an argument | Note that the executeQuery() command does not take a string (just like the PreparedStatement executeQuery() method). If you attempt to call executeQuery() on a CallableStatement with a String argument, a SQLException is thrown at runtime. |
[9.6.5]register an OUT parameter | When a callable statement takes an OUT parameter, the parameter must also be registered as such before the call. |
[9.6.6]INOUT passed an IN and then registered as an OUT | If a stored procedure has an INOUT parameter is passed the IN parameter first and then registered as an OUT parameter—eg an imaginary stored procedure t hat takes the customer ID and simply counts the orders and returns them in the same parameter. |
[9.6.7] You may or may not know if a stored procedure returns a ResultSet. | Invoking executeQuery() on a stored procedure not returning a ResultSet object throws SQLException. A good practice is to use the execute() method instead and test for a ResultSet after executing a stored procedure by using the method getMoreResults() |