title: Entity framework CREATEs against SQL Server DB nonnullable columns
body: <p>I am using EFv4 for my ORM and I just tried to insert a record into a table that has multiple columns marked as not nullable and with a default value of empty string (for <code>nvarchar</code> type columns). The problem is that EF does not pick up default values for this column and when I create an instance of my Entity but leave some string properties <code>null</code> and then try to save this in DB table an exception occurs (saying I should relax my constraint settings on dataset). </p>
  
  <p>So while the default value of empty string works from within SQL Server Management Studio (if I leave column emtpy it will insert emtpy string automatically) it does not work from within EF. </p>
  
  <p>I must say I actually noticed this before with <code>uniqueidentifier</code> primary key columns but now I see that no information about column's defaults makes it into the EF model no matter what the column is.</p>
  
  <p>Anyone else noticed this? any workarounds? </p>
  
  <p><strong>Also, if anyone know, are there any improvements around this in the latest EF Feature CTPs?</strong></p>