When using "SQL domain" constrains are checked and exception is thrown in case some required field is not entered:

Xtensive.Orm.CheckConstraintViolationException : Error 'CheckConstraintViolation' while executing query 'INSERT INTO  (...)' Original message: Cannot insert the value NULL into column 'Organization.Id', table 'xyz'; column does not allow nulls. INSERT fails.
 The statement has been terminated.
  ----> System.Data.SqlClient.SqlException : Cannot insert the value NULL into column 'Organization.Id', table 'xyz'; column does not allow nulls. INSERT fails.
 The statement has been terminated.

But for in-memory database the same code works without any problem - this bring us to problem, we can't use in-memory database for unit testing, because results from these test will be inconclusive with actual SQL domain behavior.

Is this a known issue, that will be fixed somehow soon, or is there some settings to force constrains check on in-memory database?