Bug #16649
closedgeneral problems with fulltext keys in tables (extension manager failures) 2
0%
Description
Althougt it was stated that in typo4.0.2 the problem with sql parser is fixed, it seems it is not
fro example let say I have something like the following in my ext_tabel.sql:
CREATE TABLE someextensiontable (
uid int( 11 ) NOT NULL AUTO_INCREMENT ,
pid int( 11 ) NOT NULL default '0',
title varchar( 255 ) NOT NULL ,
content text NOT NULL ,
---- etc
PRIMARY KEY ( uid ) ,
KEY parent (pid),
FULLTEXT KEY title( title ) ,
FULLTEXT KEY content( content )
) ENGINE = MYISAM DEFAULT CHARSET = utf8;
The extension manger responds with the following error:
SQL engine parse ERROR: Field type unknown in parseFieldDef()!: near "KEY content( content ) "
The code executes fine trough phpmyadmin and on the mysql client command line.
This makes me thing that there is something wrong in the SQL PARSER
I did not look at its code :(.
(issue imported from #M4399)
Updated by Michael Stucki about 18 years ago
Where did you read that fulltext keys are supported in 4.0.2? This is not the case yet.
Updated by Dmitry Dulepov almost 17 years ago
You must have space between key name and (