Mysql 4 vs Mysql 5 auto-increment field on insert?

Both the 4.1 and 5.0 docs state that 0 or NULL is required: No value was specified for the AUTO_INCREMENT column, so MySQL assigned sequence numbers automatically. You can also explicitly assign NULL or 0 to the column to generate sequence numbers.

Right.. but I'm saying that 4. X was lax in the strict policy and would allow '' and I remember old code like zen-cart and websitebaker always used '' for the autoinc field. Then when 5.

X came out, we had to go back and update all the code to use NULL instead of ''. But I'm trying to find where this was documented. – Dss Dec 30 '10 at 19:20 ok I see you linked it above and I do see the 0 or null thing.. maybe it was mysql 4.0 then.

– Dss Dec 30 '10 at 19:23.

It does not matter, mysql internally still convert to integer mysql> CREATE TABLE some_test ( id int(10) unsigned NOT NULL auto_increment, primary key(id)); Query OK, 0 rows affected (0.00 sec) mysql> insert into some_test values (''); Query OK, 1 row affected, 1 warning (0.00 sec) mysql> show warnings; +---------+------+------------------------------------------------------+ | Level | Code | Message | +---------+------+------------------------------------------------------+ | Warning | 1264 | Out of range value adjusted for column 'id' at row 1 | +---------+------+------------------------------------------------------+ 1 row in set (0.00 sec) mysql> select * from some_test; +----+ | id | +----+ | 1 | +----+ 1 row in set (0.00 sec) However, I will suggest use 0 to avoid this warning.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.