Page 1 of 1

About Question enthuware.ocpjp.v7.2.1372 :

Posted: Tue Sep 17, 2013 7:37 am
by The_Nick
Related to CallableStatement, here from the official API: http://docs.oracle.com/javase/7/docs/ap ... ,%20int%29
If the parameter is of JDBC type NUMERIC or DECIMAL, the version of registerOutParameter that accepts a scale value should be used.
What do they mean with "accepts a scale value"?

Thanks in advance.

Re: About Question enthuware.ocpjp.v7.2.1372 :

Posted: Tue Sep 17, 2013 7:56 am
by admin

Re: About Question enthuware.ocpjp.v7.2.1372 :

Posted: Sat Aug 30, 2014 1:43 pm
by hamada.yamasaki
Is there some transaction related stuff for CallableStatement vs Prepared Statement that these two statements handle differently from point of view of exam? Because i wrote some example code for callable and prepared statement but haven't benchmark the transaction performances.
Thanks

Re: About Question enthuware.ocpjp.v7.2.1372 :

Posted: Sat Aug 30, 2014 7:34 pm
by admin
No, we haven't see anything specific to CallableStatement vs PreparedStatement.

Re: About Question enthuware.ocpjp.v7.2.1372 :

Posted: Tue Apr 07, 2015 7:45 am
by winddd
A CallableStatement is easier to build and call from JDBC code than a PreparedStatement.
This is true because you don't have to write any SQL query in Java code. You just use the name of the stored procedure. The queries are already there inside the stored procedure, which exists in the Database and not in JDBC code.
Absolutely incorrect. Сreation and use in both cases is identical. The difficulties connected with SQL don't belong to a subject. Moreover, syntax for a call of procedures really is always effaced from the memory, whereas syntax of simple queries - no.

Re: About Question enthuware.ocpjp.v7.2.1372 :

Posted: Tue Apr 07, 2015 9:06 am
by admin
I agree that it is not a good option. You may expect such options in the real exam though.
thank you,
Paul.