Scott Baker wrote:
> If I create the following table, and then try and insert the following
> data both inserts work. It looks like the second one works (it shouldn't
> because Last is NULL) because it assumes Last = ''. Is there a way I can
> make it NOT assume that? If Last is not specified it should reject that
> command. Is that possible?
>
> ---------------------------------------------------------------
>
> DROP TABLE IF EXISTS foo;
>
> CREATE TABLE foo (
> ID INTEGER PRIMARY KEY AUTO_INCREMENT,
> First VarChar(30),
> Last VarChar(30) NOT NULL,
> Zip INTEGER
> );
>
> INSERT INTO foo (First, Last, Zip) VALUES ('Jason','Doolis',97013);
> INSERT INTO foo (Last) VALUES (17423);
>

In your last insert example, Last is inserted as 17423. Which is not null.

--
Thanks,
James