You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-commits@db.apache.org by Apache Wiki <wi...@apache.org> on 2007/01/30 00:52:35 UTC

[Db-derby Wiki] Trivial Update of "DerbySQLroutines" by jeanTanderson

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The following page has been changed by jeanTanderson:
http://wiki.apache.org/db-derby/DerbySQLroutines

The comment on the change is:
minor clarification for readability

------------------------------------------------------------------------------
  
  '''Procedures''' are invoked with the {{{CALL}}} statement or the {{{CallableStatement}}} method in a Java client application.  Procedures support {{{IN}}}, {{{OUT}}}, and {{{INOUT}}} parameters. If the procedure has just {{{IN}}} parameters, you can invoke it anywhere with the {{{CALL}}} statement, including in ij. If the procedure has {{{OUT}}} or {{{INOUT}}} parameters, it can't be invoked from ij, it must be invoked from a client application using the {{{CallableStatement}}} method. Starting in [http://issues.apache.org/jira/browse/DERBY-551 Derby 10.2], a java procedure can also be invoked in a trigger.
  
- Here's an example of invoking built-in procedures using {{{ij}}}. The first loads my 'myStuff.jar' jar file into the database and the second sets my database class path to include that jar:
+ Here's an example of invoking two built-in procedures using {{{ij}}}. The first, {{{SQLJ.install_jar}}}, loads my 'myStuff.jar' jar file into the database and the second, {{{SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY}}}, sets my database class path to include that jar:
  
  {{{
  ij> CALL SQLJ.install_jar