<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://introducinglinq.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>LINQ to SQL and varchar(1) fields</title><link>http://introducinglinq.com/blogs/marcorusso/archive/2008/07/17/linq-to-sql-and-varchar-1-fields.aspx</link><description>If you are using the Object Relational Designer of LINQ to SQL creating an entity of an existing table that has some VARCHAR(1) fields, you are going into this issue. The data member created in C# is char instead of string. If the field is always filled</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP2 (Build: 61129.2)</generator><item><title>Alcune segnalazioni per LINQ</title><link>http://introducinglinq.com/blogs/marcorusso/archive/2008/07/17/linq-to-sql-and-varchar-1-fields.aspx#146</link><pubDate>Sun, 20 Jul 2008 08:25:25 GMT</pubDate><guid isPermaLink="false">6f1fdd61-9c0b-497f-974b-3001d899dae0:146</guid><dc:creator>Marco Russo</dc:creator><description>&lt;p&gt;Recentemente ho scritto alcuni post in inglese nel mio blog su LINQ: Campi varchar(1) usando LINQ to&lt;/p&gt;
</description></item></channel></rss>