List:General Discussion« Previous MessageNext Message »
From:Martijn Tonies Date:November 1 2003 2:02pm
Subject:Re: "not null" and default values confusion
View as plain text  

> This question comes up a lot.  You should take a look at
> <>.  The first line
> is, "To be able to support easy handling of non-transactional tables,
> all fields in MySQL have default values."  Mysql automatically converts
> missing or illegal values to column defaults, because in the
> non-transactional case, it cannot roll back when you have an illegal
> value in the Nth row of a multi row insert.

Question: why a "rollback" - it should allow the insert in the first place,

With regards,

Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird & MS SQL Server.
Upscene Productions

"not null" and default values confusionJan Magnusson31 Oct
  • Re: "not null" and default values confusionMichael Stassen1 Nov
    • RE: "not null" and default values confusionJan Magnusson1 Nov
  • Re: "not null" and default values confusionMartijn Tonies1 Nov