[thincom2000]

Originally Posted by y2krazy

I get this when trying to import the product on 3.6.0 Gold:

Database error in vBulletin 3.6.0:

Invalid SQL:
CREATE TABLE `portfolio` (
`id` INT NOT NULL AUTO_INCREMENT PRIMARY KEY ,
`link` VARCHAR( 100 ) NOT NULL ,
`site` VARCHAR( 100 ) NOT NULL ,
`start` VARCHAR( 100 ) NOT NULL ,
`finish` VARCHAR( 100 ) NOT NULL ,
`screen1` VARCHAR( 1000 ) NOT NULL ,
`alt1` VARCHAR( 1000 ) NOT NULL ,
`screen2` VARCHAR( 1000 ) NOT NULL ,
`alt2` VARCHAR( 1000 ) NOT NULL ,
`description` VARCHAR( 10000 ) NOT NULL
) ENGINE = MYISAM ;;

MySQL Error : Too big column length for column 'screen1' (max = 255). Use BLOB instead
Error Number : 1074
Date : Saturday, August 12th 2006 @ 09:23:27 PM
Script : http://www.transitracing.com/admincp...=productimport
Referrer : http://www.transitracing.com/admincp...?do=productadd
IP Address : *****
Username : Thermo.
Classname : vb_database

I don't think this was touched on, but the reason this happened is because VARCHARs larger than 255 are not supported unless your server runs MySQL 5. Once everyone starts running 5, we can stop using BLOBs. I prefer LONGTEXT myself, since for some reason I can never use any string functions like explode() or str_replace() on a BLOB stored in a string, the string just gets set equal to ''

Also, I got excited when it sunk in that I upgraded to PHP 5, but then also realized I wouldn't be able to write hacks with any of the new functions if I expected to post them here and have the code work for most people.

But I also had an XML error that made no sense why it wasn't creating my database. I just deleted most of the file and started over, since after 2 days I couldn't find the syntax error. vBulletin wasn't reporting it during Product Installation, and it remained hidden even after using $db->show_errors();

This error had just reminded me of all that. Sorry, guys.