installation problem while connecting to database

[krishnmx]

I am getting this error while installation

3) Create Database Tables

The following error occurred:


• You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'TYPE=MyISAM DEFAULT CHARSET=utf8' at line 6

[Ben]

Hi Krishnmx,

Interesting... judging from the error, there's a couple of things it might be: the UTF8 charset isn't installed or you don't have the MyISAM engine type (this is just the way the database information is actually stored behind the scenes). Both of those are available in all out-the-box installations of MySQL.

Do you have phpMyAdmin access? If so, you could connect to your DB and run some queries on your database to find out what's available. Try running these queries one by one:

Code:

SHOW ENGINE InnoDB STATUS
SHOW ENGINE MyISAM STATUS
SHOW CHARACTER SET

This would at least help identify the problem. But I should note: Form Tools *requires* the UTF-8 charset and the MyISAM engine.

- Ben

[avtomatron]

This would at least help identify the problem. But I should note: Form Tools *requires* the UTF-8 charset and the MyISAM engine.

Solved (via google):

you must replace
TYPE=MyISAM
in all formtools files with
ENGINE=MyISAM

[dbennett]

Same problem.

Fedora Core 14
MySQL 5.5.11
PHP 5.3.6

Here are some quick fixes from the Unix command line:

From formtools top directory

1) Determine if you have the problem:

find . -type f -exec grep -Hi type=myisam {} \;

(no results == no problem)

2) Fix the problem:

find . -type f -name '*.php' -exec perl -pi.bak -e 's/TYPE=MyISAM/ENGINE=MyISAM/gi;' {} \;


3) Delete the backup files after fixing:

find . -type f -name '*.bak' -exec /bin/rm {} \;


(then run 1 again)

--Dave

[Ben]

Hey Dave,

Thanks for posting this. Huh! Originally, I had it set as ENGINE=MyISAM but that threw errors on some system, so I changed it to TYPE=MyISAM. Reading up on it now, however, I gather that ENGINE is newer and TYPE is deprecated. I'll keep looking around, but I would imagine there's a way I can detect to see which one's supported on each system. If so, I'll get this fix into 2.1.0.

Thanks!

- Ben