Closed GoogleCodeExporter closed 9 years ago
pls help asap, i have searched it for several days~
Original comment by scarlett...@gmail.com
on 4 Nov 2010 at 11:05
Hi Xu Han Zi. Please post this also to the mailing list.
groups.google.com/group/mybatis-user
Maybe other users can help.
Original comment by eduardo.macarron
on 4 Nov 2010 at 1:02
Hi eduardo,
thanks for your suggestions.
Any comments from you for this problem?
Original comment by scarlett...@gmail.com
on 5 Nov 2010 at 7:18
I have posted this issue on stackoverflow.com:
http://stackoverflow.com/questions/4104116/mybatis-sybase-stored-procedure-retur
ns-zero-rows
Original comment by kospiotr
on 5 Nov 2010 at 7:24
Hi kospiotr,
Thank you!
But you have missed some parts during copy.
ormally the result should be:
<code>
DEBUG PreparedStatement - ==> Executing: {call tempdb..testSP ?}
DEBUG PreparedStatement - ==> Parameters: mydata(String)
DEBUG ResultSet - <== Columns: result1, result2
DEBUG ResultSet - <== Row: 1, mydata
</code>
from the result, we can see it get the result succesfully.
but you put as
DEBUG PreparedStatement - ==> Executing: {call tempdb..testSP ?}
DEBUG PreparedStatement - ==> Parameters: mydata(String)
DEBUG ResultSet -
couls you pls revise it a little?
Original comment by scarlett...@gmail.com
on 5 Nov 2010 at 8:05
You are using the wrong syntax for calling stored procedures. Change it to
this (note the added parentheses):
{call tempdb..testSP (#{in})}
Original comment by jeffgbut...@gmail.com
on 5 Nov 2010 at 11:10
[deleted comment]
I'm going to assume this is working now after the fix in comment 6. If you
still have a problem with this, please ask on the user list first.
Original comment by jeffgbut...@gmail.com
on 29 Dec 2010 at 11:51
Original issue reported on code.google.com by
scarlett...@gmail.com
on 4 Nov 2010 at 11:01Attachments: