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
|
Originally, my stored procedure had a single output parameter, which LightSpeed designer marked as "Direction" "Ref". As such, I am able to call the stored procedure from the unit of work, passing ref [variable] for my variable, and it was set properly. I added a second output parameter, with "Direction" "Ref" as the previous one, and when I call it from the unit of work, by passing both variables with "ref", neither are assigned any value. The stored procedure, when run manually from a SQL query, has values for both output parameters. I am using LightSpeed 4.0. Please advise. Thanks, ~Bill |
|
|
Hi Bill, Ive set up a couple of test cases here and I am seeing all output or input/output (ref) variables getting assigned back the correct values after being called. Are you able to send through a small repro project for this (should just need to contain the stored procedure and returning entity type in the model and a quick example of the failing call) and I can have more of a look into this for you.
|
|
|
See attached PDF (because it includes screenshots) |
|
|
Also, be advised, the problem persists if I try returning a much smaller decimal, i.e. a decimal(10,2) from SQL... |
|
|
I found this thread: http://www.mindscapehq.com/forums/thread/257487 in which the user was having the exact same issue, however, in a nightly build it was fixed. I am hesitant to use a nightly built in our production environment, so... does Mindscape have any comments on using unreleased, nightly builds, in a production environment? Thanks, ~Bill |
|
|
The latest nightly build seemed to fix both issues, but still does Mindscape have any comments on using unreleased, nightly builds, in a production environment? Thanks, ~Bill |
|
|
Hi Bill, The nightly builds are run through our unit test suite each night so this covers off all of the basic functionality assumptions and a large number of defect case repros we have seen over the lifetime of the product. There are roughly 23000 unit tests in the suite and it has pretty reasonable coverage so this gives a good baseline against regressions. We would certainly advise you to perform your own testing, but in general we feel the nightly builds are reasonably stable and we dont generally see regressions occurring - however functionality could change in response to actual bug fixes so you do need to watch for that :)
|
|