Re: Problem with IN parameters to an Oracle stored procedure
- From: "joeNOSPAM@xxxxxxx" <joe.weinstein@xxxxxxxxx>
- Date: Thu, 08 Nov 2007 16:08:41 -0000
On Nov 8, 12:34 am, swetha <swethasiva...@xxxxxxxxx> wrote:
On Nov 7, 4:03 pm, "joeNOS...@xxxxxxx" <joe.weinst...@xxxxxxxxx>
wrote:
what happens if you change the procedure definition to have all
the parameters defined as NUMBER
Tried that now. No luck. Still the same.
, or NUMBER (20,0)?
What do you mean by that?
clientID IN NUMBER (20,0)
gives me a compile error.
nevermind. So if you do this:
CallableStatement cs = conn.prepareCall("{call InsertValue(?, 1, 1,
235234)}");
cs.registerOutParameter(1, Types.INTEGER);
boolean result = cs.execute();
int ID = cs.getInt(1);
does it work?
I would make a simple standalone program that creates it's own
table, inserts a row or two, and creates a procedure with the
same signature as yours, and then duplicates the problem. That
would be perfect for Oracle support.
Joe
.
- Follow-Ups:
- References:
- Problem with IN parameters to an Oracle stored procedure
- From: swetha
- Re: Problem with IN parameters to an Oracle stored procedure
- From: joeNOSPAM@xxxxxxx
- Re: Problem with IN parameters to an Oracle stored procedure
- From: swetha
- Problem with IN parameters to an Oracle stored procedure
- Prev by Date: Re: Problem with IN parameters to an Oracle stored procedure
- Next by Date: Re: Problem with IN parameters to an Oracle stored procedure
- Previous by thread: Re: Problem with IN parameters to an Oracle stored procedure
- Next by thread: Re: Problem with IN parameters to an Oracle stored procedure
- Index(es):
Relevant Pages
|
