This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hi, I've been struggling for some time, when I finally realised that while in my stored procedure the IN parameter was "este_u", in the designer the name was "esteu", and the parameter name was empty, thus meaning it was trying to call the procedure with "esteu" which obviously returned an ora error. in the model, it produced this line: ProcedureParameter esteUParameter = new ProcedureParameter("esteU", esteU); instead of this one: ProcedureParameter esteUParameter = new ProcedureParameter("este_U", esteU); If for some reason it can't be automatically completed in with the right parameter name, at least some kind of warning would be nice... (check your "parameter names") (or maybe it's a bug?) Just an ideea. Thanks guys |
|
|
|
|
Thanks for alerting us to this. We've reproduced the issue and implemented a candidate fix which will be included in the 10 April nightly build, available from about 1500 GMT. Please let us know if you still see this problem after upgrading to that nightly build. |
|
|
|
