It's possible that when importing a MySQL dump file via the command line you may hit this error once in a while.

Usually, it's because there is a discrepancy between the MySQL server, setup, version, or configuration from where the original MySQL database was exported or resides.

"mysqldump" is a common command for exporting a database, often used when attempting to transfer a MySQL database from one server to another (such as from a staging to development or production environment).

The error "The used table type doesn't support FULLTEXT indexes" is one that usually has the potential to cause havoc if not resolved, if returned during the import of your database.

If unresolved, you could face a plethora of issues that may prevent writing to the database via a PHP application.

So, without delving too deep and taking you off track, there is a quick workaround solution to this problem that will have you on your way fairly swiftly.

1. Open your .sql database file on your local machine
2. Run a 'find' for all occurrences of ENGINE=InnoDB and replace all with ENGINE=MyISAM
3. We do this because MySQL versions prior to 5.6 do not support FULLTEXT indexes with the InnoDB engine. However, they are supported by MyISAM.
4. Save your file, and try importing this modified version of the SQL file instead.

If everything works as intended, you should find that you're able to import the database smoothly and without errors.