ImpEx "slight problem with database"

[cyburbia]

Finally got my database restored. Lost about six hours of posts. I'm not even going to touch Impex until it's proven to be bug-free for a vBullting 3.0.* -> 3.5 merge.

[Tru2Chevy]

I seem to be having a similar problem, and I admittedly don't really know what I'm doing when it comes to playing with the database. Would someone be willing to give me a few simple step-by-step instructions to fix this?

Thanks!


This is with vb 3.5 Gold and the latest ImpEx download. Attempting to import from a phpBB 2.0.17 board.

- Justin

Database error in vBulletin:ImpEx Target :

Invalid SQL: CREATE TABLE `vbfields` (
`fieldname` varchar(50) NOT NULL default '',
`tablename` varchar(20) NOT NULL default '',
`vbmandatory` enum('Y','N','A') NOT NULL default 'N',
`defaultvalue` varchar(200) default 'NULL',
`dictionary` mediumtext NOT NULL
);

mysql error: You have an error in your SQL syntax near ';
' at line 7

mysql error number: 1064

Not to sound impatient or anything, but could I get some help with this error please?

Thanks to anyone who takes the time to help out a newb...

- Justin

[Tru2Chevy]

Ok, just so we are clear on the fix, here is the block of code the way it should look:

$queries[] = "CREATE TABLE `{$tableprefix}vbfields` (
`fieldname` varchar(50) NOT NULL default '',
`tablename` varchar(20) NOT NULL default '',
`vbmandatory` enum('Y','N','A') NOT NULL default 'N',
`defaultvalue` varchar(200) default 'NULL',
`dictionary` mediumtext NOT NULL
)";

- Justin

[Jerry]

This has been fixed in the latest download.

[cujo]

I seem to be having a similar problem, and I admittedly don't really know what I'm doing when it comes to playing with the database. Would someone be willing to give me a few simple step-by-step instructions to fix this?

Thanks!


This is with vb 3.5 Gold and the latest ImpEx download. Attempting to import from a phpBB 2.0.17 board.

- Justin

Manually edit vbfields.php and change the ); to just )

Worked for me.

[cujo]

ooops, missed Page 2

[aladinliverpool]

This has been fixed in the latest download.

so does this now support migration of data between 3.0.* to 3.5 properly?