Adding Guid field causes exception in migrations (SQLLite)

Steps: In designer:

1. Create new database model
2. Create new entity
3. Create migration
4. Add field with type Guid, and IsNullable set to false
5. Create another migration
6. Try to create new database -> System.Data.SQLite.SQLiteException : SQLite error Cannot add a NOT NULL column with default value NULL

Exception occurs in Up() method of generated migration class, on line:

this.AddColumn("Entity", null, "GuidField", ModelDataType.Guid, false);

If I skip step 3, and make only one migration, everything works fine.

Checked on version: 4.0.1339.20408 and 4.0.1190.19937 SQLLite

This will be addressed in the next nightly build.

However, in a way this is SQLite trying to alert you to a real issue. Supplying a default is safe when the table is empty (and it is silly that SQLite requires one in this case), but if the table already contains rows, then there is no good value that we can provide as a default -- every existing row will be given the same GUID (in this case Guid.Empty). By supplying a default we are preventing SQLite from warning you about the latter issue. So it's important to take care that Add Column migrations are applied only to empty tables, or to ensure that your application code handles empty GUIDs correctly.

Thank you, for your answer.

Yes, I'm aware, that my code must take care about Guid.Empty values.