You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Jeff Sexton <js...@odshp.com> on 2003/05/02 22:52:49 UTC

Re: esql stored procedure problem - one solution

For jConnect/Sybase, using a PreparedStatement instead of a
CallableStatement for a stored procedure works if the
allow-multiple-results option is also used.  Prior to the fragment below,
I build the "call myProc p1, p2, p3" statement as a StringBuffer, then
exec it like this:

    <esql:connection>
      <esql:allow-multiple-results>yes</esql:allow-multiple-results>
      <esql:pool>odsdb02_pool</esql:pool>
        <esql:execute-query>
          <esql:query>
            <xsp:expr>queryString.toString()</xsp:expr>
          </esql:query>
          <esql:results>
            <esql:row-results>
              <esql:get-string column="MyColumn"/>
            </esql:row-results>
          </esql:results>
          etc....

This works!

Whew, what a long day....



---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-users-help@xml.apache.org