\nFor those of you who's blog readers don't always get updated (rather than brand new) blog entries, there's a happy ending to my last "fixed-almost" blog entry on EDM 4.0 and parameterization. I've heard that this has been fixed to generate VARCHAR(8000) parameters and also that the unparameterized version:\n<\/p>\n
\nvar x = from a in ents.authors
\n where a.au_lname == "Smith"
\n select new { a.au_lname, a.au_fname };\n<\/p>\n
\nwill generate …WHERE au_lname = 'Smith' instead of …WHERE au_lname = N'Smith'.\n<\/p>\n
\nNote that this is a different semantic; they generate a parameter type that agrees with the column's data type rather than using the .NET string type's data type equivalent (NVARCHAR). This will be better for performance because the database and parameter types agree.\n<\/p>\n
\nFix is coming in next beta version of .NET 4.0. I've updated the original blog entry to note this as well.<\/p>\n","protected":false},"excerpt":{"rendered":"
For those of you who's blog readers don't always get updated (rather than brand new) blog entries, there's a happy ending to my last "fixed-almost" blog entry on EDM 4.0 and parameterization. I've heard that this has been fixed to generate VARCHAR(8000) parameters and also that the unparameterized version: var x = from a in ents.authors […]<\/p>\n","protected":false},"author":7,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[12],"tags":[],"class_list":["post-644","post","type-post","status-publish","format-standard","hentry","category-data-access"],"yoast_head":"\n