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
|
I installed last night's build (5/16/2014 = 5.0.2795.0), which I assume included the latest designer for Visual Studio 2013. When I set a stored procedure's out parameter "size" to support "MAX" i.e. nvarchar(MAX), the LightSpeed generated code overrides my "-1" to be null: ProcedureParameter messageBodyParameter = new ProcedureParameter("messageBody", null, System.Data.ParameterDirection.Output, System.Data.DbType.String, null, null, null); Which results in the stored procedure failing, indicating that string values can't have a size of zero (or something similar). If I manually modify the generated code, it seems to work fine: ProcedureParameter messageBodyParameter = new ProcedureParameter("messageBody", null, System.Data.ParameterDirection.Output, System.Data.DbType.String, -1, null, null); Is this an actual bug? Am I doing something wrong? Is my designer not the latest? Thanks! |
|
|
|
|
Thanks for reporting this, we dont expect a value less than 1 so if we see this then we assume the parameter is null. Ill look at adding in support for this to allow this to function as you would expect and aim to get this into the nightlies this week.
|
|
|
|
|
This appears to not have been corrected yet as of the 5/27 nightly build (5.0.2806). Therefore, currently, LightSpeed (designer) doesn't support stored procedure (MAX) out parameters :( Please advise, Thanks, ~Bill |
|
|
|
|
Hi Bill, We havnt released an update for this into the nightlies yet so there is no change in the functionality, Ill let you know once this is merged in.
|
|
|
|
|
Hi Bill, An update for this has been merged in today so this will be available in the next nightly build. Let us know if you have any issues after being able to update.
|
|
|
|
