R – Prevent nullable parameter in stored procedure with LINQ

asp.netlinqstored-procedures

I want to define stored procedure parameters which do not allow null arguments.

alt text http://www.pixelshack.us/images/xg3mr2xw0q13z22nal.jpg

That @MailItemId int OUTPUT will be not nullable because when I import the stored procedure into the LINQ to SQL designer it says @MailIetmid is ref int? mailItemId.

alt text http://www.pixelshack.us/images/er80hukg27lreiy9b83y.jpg

Thanks.

Best Answer

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.

Related Solutions

C# – How to handle a NULLable Int column returned from a stored procedure in LINQ to SQL

You need to declare the variable to be nullable. In the designer, click the property in your model that needs to be nullable, and then in the Properties window, set the "Nullable" property to True. This will tell the generator to create your property as Nullable<int> or int?

Sql – Insert results of a stored procedure into a temporary table

You can use OPENROWSET for this. Have a look. I've also included the sp_configure code to enable Ad Hoc Distributed Queries, in case it isn't already enabled.

CREATE PROC getBusinessLineHistory
AS
BEGIN
    SELECT * FROM sys.databases
END
GO

sp_configure 'Show Advanced Options', 1
GO
RECONFIGURE
GO
sp_configure 'Ad Hoc Distributed Queries', 1
GO
RECONFIGURE
GO

SELECT * INTO #MyTempTable FROM OPENROWSET('SQLNCLI', 'Server=(local)\SQL2008;Trusted_Connection=yes;',
     'EXEC getBusinessLineHistory')

SELECT * FROM #MyTempTable

Best Answer

Related Solutions

C# – How to handle a NULLable Int column returned from a stored procedure in LINQ to SQL

Sql – Insert results of a stored procedure into a temporary table

Related Topic