You can specify a default value instead:
@MailItemId int OUTPUT = 0
or something like that
Polaris878
2009-07-26 01:01:17
A:
That doesn't prevent the type being nullable, it just defines a default value which is not null. The two things are orthogonal.
Greg Beech
2009-07-26 01:19:57
+1
A:
If nothing else, you can just modify the auto-generated code (in designer.cs) to not accept a nullable integer. If the parameter ever does end up being null, it will probably cause a weird exception down in the LINQ to SQL code, but that's not a huge deal.
Rex M
2009-07-26 01:23:32
It seems pretty useful to me. So I'll try it right away. I'll tell you whether it will work or not :) But thanks for the answer.
Braveyard
2009-07-26 08:56:39
A:
You could create a function instead that returns an INT.
On the other hand, it is possible from SQL point of view that a NULL can be returned from function. I don't know how code generator will generate function for that. If it still returns a nullable int, I don't think it could be possible.
shahkalpesh
2009-07-26 01:37:17