Bug when inserting null in a column with a default value

Bug when inserting null in a column with a default value

Postby crazypit » 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.
crazypit
 
Posts: 163
Joined: Wed 15 Apr 2009 08:43

Postby AndreyR » Thu 23 Jul 2009 14:25

Please make sure that you have set the Auto Generated Value property to true for this column.
AndreyR
Devart Team
 
Posts: 2919
Joined: Mon 07 Jul 2008 13:16


Return to LinqConnect (LINQ to SQL support)