I am working on finalizing an implementation to support functionality simliar to: http://weblogs.asp.net/jeffreyzhao/archive...expression.aspx

I have the following LINQPad select statement:



When I run an update batch statement (don't worry I plan on blogging about this whole thing once I've ironed out everything), essentially the SQL command text to run will be:



Now, if I take that *exact* SQL to QueryEx or SQL Management Studio, it runs fine, but LINQPad returns an error of:

SqlException: Must declare the scalar variable "@Author0". Incorrect syntax near the keyword 'AS'.

LINQPad obviously display more information I can append if needed, but that is a start. Any ideas to why it wouldn't work only in LINQPad (admittedly I've yet to write a little test app to test it in stand alone C# application).

I 'mis-titled' this post. Sorry, dont' know if forum moderators want to fix it or not. Should be titled: Wierd Linqpad Update Behavior

This post has been edited by Terry Aney: Apr 11 2008, 08:56 PM

Hi Terry

Maybe I'm missing something, but I don't see how that SQL could possibly execute in Management Studio or Query Express without first populating the parameters:



Regards

Joe

Well you are right. I made the assumption you'd 'assume' that. However I figured out the problem. When creating a command string for DataContext.ExecuteCommand(), the parameters must be named @p0-N. I was naming them 'other than' that, but also providing the same 'new' name in the DbCommand.

However, when calling ExecuteCommand() you pass only the string and object[] of values for params and it takes the object[] and creates new parameters @p0-N. Stupid mistake on my part. I almost have this extension tested thoroughly enough to blog about. You should be seeing something soon.

Cool - will look forward to seeing it!

Cheers

Joe

Joe,

Here is the article: http://www.aneyfamily.com/terryandann/post...INQ-to-SQL.aspx

Also made apologies in there for ever suspecting LINQPad in the first place

Enjoy.

Just read the article - it looks really useful.

Highly recommended!

Joe

Thanks Joe. Couple things. First, is it worth you changing the title of the post as it is a bit misleading? Not sure if you want to or not.

More importantly, I've found and posted a new fix in the code. You can read about the issue and the fix at LINQ to SQL Batch Updates/Deletes: Fix for 'Could not translate expression'.

Hi Terry,

I updated the topic title as you suggested so it's clear for other people.

Thanks for pointing that out!
Sarah

I don't even remember what the 'original' title was, but I think you updated it to 'Wierd Linqpad Update Behavior' (or at least that is title currently showing). Nothing really wierd/wrong with LINQPad...I made a mistake. The post has evolved more into a 'Batch Updates and Deletes with LINQPad/LINQ to SQL'. Again, you can review if you want to change it to something along those lines.