While reviewing LINQ TO SQL with a colleague recently I discovered yet another "hickup" in v 1.0 of LINQ TO SQL.

I did a search for uploading an image (or any file) using LINQ TO SQL and could not find a blog or article. Here is a quick note on how to do this. The following code assumes that you have a "FileUpload" control on your webform. I'm using a stored procedure to add a row to my "Users" table. I have a column named "Photo". The sql server datatype for Photo column is "Image".

Earlier this week I ran into a problem with LINQ and building a Dynamic query. The issue is I wanted to build a search string based on the data in my function parameters.

ran into my first problem with LINQ TO SQL a couple of days ago and forgot about it. I ran into again today and decided to let everyone know about it. What I ran into was if you change an underlying table in SQL Server there is not a way to "refresh" or "sync" the table in the LINQ TO SQL Designer. The only way to get the updated table is to delete the current table from the designer and then add it again to the designer.

Ran across a small issue with LINQ TO SQL I'd like to share. As you may or may not know LINQ TO SQL's default behavior when retrieving a result set from the database for an entity is to keep that object in cache. If you run another query against linq attempting to retrieve the same row, LINQ will return the cached object. Depending on how you want your program to behave this can be a good thing or a bad thing. For me, this was a bad thing.