Ok been doing some more research on this issue.
I'm using MySQL 5.0.77
From what I have read that in MySQL 4 and prior, if a column is set to ' ', it was just converted to a zero value but in MySQL 5 it will spit out the error "Incorrect integer value".
Further reading into this matter suggests its a sql_mode issue. It is suggested to get the old MySQL 4 behaviour back that one should execute set sql_mode = ' '; which they said an empty string means Traditional MySQL mode.
(if I'm wrong guys feel free to correct me at anytime!
)
Since the default value is empty (no modes set) and that is what set sql_mode = ' ' does.... I cleared my SQL Mode, left it empty. This setting is in your my.ini file (for those like me that didn't know :p ). There are a few different ways to access it. Directly by just finding your my.ini file and clear the SQL MODE... another way is to load up MySQL Administrator and goto Startup Variables, Click on Advanced Tab then slide about midway down in the Various box you you will find SQL Mode: You can clear it here as well.
Now after clearing this. I deleted my spells_new table. Sourced in the 230_spells_table.sql unmodified. Ran Perl import_spells.pl and it reported no errors and I had a full listing of spells (14799 of 14799).
So it was me all this time! Gah. What got me to do further research was when I tried to update my PEQ DB editor and the isbot filed spit out the error "Incorrect integer value". I looked on the boards, found no one else having this problem so off to Google I went. A few seconds later I found what my problem was. Sheesh.
So the moral of the story...... Search the Boards, Google it and do some research.
Anyways, just thought I would share