Columns are always NotNullable (as a default)

I have the following migration (one of many, and it is a typical ASP.NET Identity table):

Create.Table("aspnet_users")
    .WithColumn("id").AsGuid().PrimaryKey().NotNullable()
    .WithColumn("username").AsString()
    .WithColumn("normalized_username").AsString()
    .WithColumn("email").AsString()
    .WithColumn("normalized_email").AsString()
    .WithColumn("email_confirmed").AsBoolean().NotNullable()
    .WithColumn("password_hash").AsString()
    .WithColumn("security_stamp").AsString()
    .WithColumn("concurrency_stamp").AsString()
    .WithColumn("phone_number").AsString()
    .WithColumn("phone_number_confirmed").AsBoolean().NotNullable()
    .WithColumn("two_factor_enabled").AsBoolean().NotNullable()
    .WithColumn("lockout_end").AsDateTime()
    .WithColumn("lockout_enabled").AsBoolean().NotNullable()
    .WithColumn("access_failed_count").AsInt32().NotNullable()
    .WithColumn("display_name").AsString();

My assumption was that unless NotNullable is specified the column would default to Nullable. However after the migration has ran, all the columns are NotNullable.

I’m using Postgresql. Am I doing something wrong?

[jzabroski]

It also seems as though SQL Server lets you change the default behavior of implicit syntax, so FluentMigrator should explicitly specify null or not null. See: SET ANSI_NULL_DFLT_ON:

This setting only affects the nullability of new columns when the nullability of the column is not specified in the CREATE TABLE and ALTER TABLE statements. When SET ANSI_NULL_DFLT_ON is ON, new columns created by using the ALTER TABLE and CREATE TABLE statements allow null values if the nullability status of the column is not explicitly specified. SET ANSI_NULL_DFLT_ON does not affect columns created with an explicit NULL or NOT NULL.

[jzabroski]

Thanks for offering to help, and it’s wecome. To be quite honest, just answering questions takes a lot of my and @fubar-coder 's time. I don’t think we get enough development time to actually improve things. So picking off some easy tasks would definitely help towards adding features. I feel this will be a good year roadmap wise, as I have finally come up with some decisions around how to support multiple target framework monikers.