Bug when inserting null in a column with a default value
Posted: Thu 23 Jul 2009 11:10
Hello,
I use the latest version of dotConnect for Oracle.
I insert an Entity using Linq and for a property which is defined as not nullable in database, i get a "Cannot insert null in column" error when i don't provide a value. Nevertheless, in the database i defined a Default value for the column.
The engine should allow the insertion of such a property. If i need to provide a value, then the Default option in my database is obsolete and cannot really use it.
I really can't tell if this is a general issue of the dotConnect provider or specific to "Linq To Sql" support. But the Microsoft for Oracle provider allows such an insertion.
I use the latest version of dotConnect for Oracle.
I insert an Entity using Linq and for a property which is defined as not nullable in database, i get a "Cannot insert null in column" error when i don't provide a value. Nevertheless, in the database i defined a Default value for the column.
The engine should allow the insertion of such a property. If i need to provide a value, then the Default option in my database is obsolete and cannot really use it.
I really can't tell if this is a general issue of the dotConnect provider or specific to "Linq To Sql" support. But the Microsoft for Oracle provider allows such an insertion.