Here is my solution fo MS SQL Server. I think Sybase is a copy of MS SQL Server:

in the ibatis map file:
<parameterMap id="procedure_seq_Result" class="map">
<parameter property="m_value" javaType="java.lang.String"
 jdbcType="VARCHAR" mode="OUT"/>
</parameterMap>

<procedure id="my_seq_nextval"
parameterMap="procedure_seq_Result">
{call $m_name$(?) }
</procedure>

in the dao class:

     Map map_param = new HashMap(2);
     map_param.put("m_name", sequence_name);

     getSqlMapClientTemplate().insert(
            "my_seq_nextval", map_param);
     return ((String)map_param.get("m_value"));

-Henry

Priyesh Mashelkar wrote:

I hope the '..' in client_reporting..CLT_language_lookup_q1 is not the problem 
here!!!

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 09, 2005 7:08 PM
To: user-java@ibatis.apache.org
Subject: Re: SQLMaps - Sybase and stored procedures


Thanks.

I have tried both regular jdbc and sybase jdbc calls i.e.

sybase --> {call client_reporting..CLT_language_lookup_q1 @from_text=?,
@language=? }
jdbc --> {call client_reporting..CLT_language_lookup_q1 (?,?) }

Both attempts failed with the same sql exception (see previous thread
entry).


Thanks,
andy


PS: I am using iBatis SQLMaps 2.1.5.




MASTEK
"Making a valuable difference"
Mastek in NASSCOM's 'India Top 20' Software Service Exporters List.
In the US, we're called MAJESCO

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Opinions expressed in this e-mail are those of the individual and not that of 
Mastek Limited, unless specifically indicated to that effect. Mastek Limited 
does not accept any responsibility or liability for it. This e-mail and 
attachments (if any) transmitted with it are confidential and/or privileged and 
solely for the use of the intended person or entity to which it is addressed. 
Any review, re-transmission, dissemination or other use of or taking of any 
action in reliance upon this information by persons or entities other than the 
intended recipient is prohibited. This e-mail and its attachments have been 
scanned for the presence of computer viruses. It is the responsibility of the 
recipient to run the virus check on e-mails and attachments before opening 
them. If you have received this e-mail in error, kindly delete this e-mail from 
all computers.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~



Reply via email to