I think either your explain is wrong, or the manual explain is wrong. exerpt:
<manual version="7.6 chm"> A CONSTRAINT definition defines an integrity condition that must be fulfilled by all the column values in the columns defined by the column definition with CONSTRAINT definition. The CONSTRAINT definition for a column is checked when a row is inserted and a column changed that occurs in the CONSTRAINT definition. If the CONSTRAINT definition is violated, the INSERT or UPDATE statement fails. **When you define a constraint, you specify implicitly that the NULL value is not permitted as an input.** </manual> As seen in above paragraph... What is right? Thanks, Edson Richter > Edson Richter wrote : >> >>Why could not MaxDB accept NULL values in columns with CHECK >>constraint? There are any SQL >>standards that dictates this rule (I really never heard about this)? >> >>Can I fill a request to add this feature? >> >>Thanks, >> >>Edson Richter >> > > MaxDB accepts null values for constraint columns, if the constraint does. > Example : > > create table test (col1 int check col1 > 0) > > will not accept null values because null > 0 is not true. > > create table test (col1 int check col1 is null or col1 > 0) > > will accept null values. > > Best Regards, > Thomas > > -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
