Issue Bug Closed

#16649general problems with fulltext keys in tables (extension manager failures) 2

Krassimir Berov 10/17/06, 13:50 updated 08/06/10, 13:19

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)

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.