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 have a stored procedure which has an integer input parameter. When I set the type of the parameter in the designer to an LS UDT (an enumeration) the type in the generate coded is "object" rather than the type I specified, is that expected? Sample LS generated code
I expected the feeType parameter to be Common.Enumations.FeeType Code currently works just no type checking. LS4 Release running against MSSQL 2K8R2 Bryn |
|
|
Hi Bryn, Yes, currently this is expected behavior - we dont add UDT type details when generating our the procedure definition. I will have a look into whats involved in getting this updated though as it would be useful to tighten this up :)
|
|
|
Hi Jeremy, It would be good to tighten this up:) I was tripped up by this when I changed an sproc parameter type, "refreshed" the sproc reference in the LS designer, then the application died at runtime in the one place where I had missed changing the code. Improved compile time support would be great. "Help developers fall into the pit of success" (http://www.codinghorror.com/blog/2007/08/falling-into-the-pit-of-success.html) Bryn |
|
|
Hi Bryn, Thanks for alerting us to this. As of the next nightly build, procedure parameters of user-defined types (such as enums) will be correctly emitted as the appropriate CLR type so that you will get compile time safety. |
|
|
Hi Ivan & co, That's great thanks. Bryn |
|
|
Hi Ivan & co, That's great thanks. Bryn |
|