Not sure whether this is part of LinqPad or the Framework, but if you have a Sql table with a column of type NVarChar and length 1, then it is mapped to char? instead of string? which causes a problem if the column contains an empty string.

Is there a way of fixing this?

Good point. LINQPad maps char(1) columns to a char type from version 1.35 to be consist with SqlMetal and Visual Studio's designer.

You can disable this in Edit | Preferences | Query although this will disable support for 1:1 relationships as well. Perhaps I should decouple these two things in the next update.

Joe

Thanks. If you could decouple them it would be great as the 1:1 relationships is too nice a feature to lose.

That was really a great post and information - just bookmarked and keep up the good work

You might like to download the latest preview of LINQPad:
http://www.linqpad.net/preview/LINQPad.exe

I've permanently disabled the mapping of nvarchar(1) to char - it now maps to string instead.

nchar(1) and char(1) however, still map to the char type.

This should take care of nearly all scenarios.

Joe

Yes, that works fine.

Thank you very much.