Project

General

Profile

Actions

Bug #16649

closed

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

Added by Krassimir Berov about 18 years ago. Updated over 14 years ago.

Status:
Closed
Priority:
Should have
Category:
-
Target version:
-
Start date:
2006-10-17
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.0
PHP Version:
4
Tags:
Complexity:
Is Regression:
Sprint Focus:

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)


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #18251: FULLTEXT keys are not processed correctlyClosedDmitry Dulepov2008-02-19

Actions
Actions

Also available in: Atom PDF