Project

General

Profile

Actions

Bug #24411

closed

Error messages using DB compare function with tables definitions from real_url extension

Added by Adrian Fischer almost 14 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2010-12-25
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.5
PHP Version:
5.2
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

Using the DB compare function shows the following erros:

Error 1:
BLOB/TEXT column 'pagepath' used in key specification without a key length

SQL-Statement 1:
CREATE TABLE tx_realurl_pathcache ( cache_id int(11) NOT NULL auto_increment, page_id int(11) NOT NULL default '0', language_id int(11) NOT NULL default '0', rootpage_id int(11) NOT NULL default '0', mpvar tinytext NOT NULL, pagepath text NOT NULL, expire int(11) NOT NULL default '0', PRIMARY KEY (cache_id), KEY pathq1 (rootpage_id,pagepath(32),expire), KEY pathq2 (page_id,language_id,rootpage_id,expire), KEY expire (expire) ) ENGINE=InnoDB;

Error 2:
Specified key was too long; max key length is 1000 bytes

SQL-Statement 2:
CREATE TABLE tx_realurl_uniqalias ( uid int(11) NOT NULL auto_increment, tstamp int(11) NOT NULL default '0', tablename varchar(255) NOT NULL default '', field_alias varchar(255) NOT NULL default '', field_id varchar(60) NOT NULL default '', value_alias varchar(255) NOT NULL default '', value_id int(11) NOT NULL default '0', lang int(11) NOT NULL default '0', expire int(11) NOT NULL default '0', PRIMARY KEY (uid), KEY tablename (tablename), KEY bk_realurl01 (field_alias(20),field_id,value_id,lang,expire), KEY bk_realurl02 (tablename(32),field_alias(20),field_id,value_alias(20),expire) );

Apache: 2.2.16
PHP Versionen: 5.2.14
mySQL Version: 5.0.91-community-log
(issue imported from #M16839)

Actions #1

Updated by Adrian Fischer almost 14 years ago

Both statements are executed without error using phpMyAdmin.

I used TYPO3 trunk revision 9892.

Actions #2

Updated by Christian Hernmarck over 13 years ago

  • Target version deleted (0)

Seems to be a dbal problem.
when disabling dbal the install tool can create the needed tables - with dbal enabled the mentioned error appears...

That's why it also works within phpMyAdmin....

/Christian

Actions #3

Updated by Adrian Dymorz over 13 years ago

Yes, I was using dbal. (And yes, I changed my name :-))

Actions #4

Updated by Alexander Opitz over 10 years ago

  • Description updated (diff)
  • Status changed from New to Needs Feedback
  • Is Regression set to No

Hi,

as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (4.5.35 or 6.2.4)?

Actions #5

Updated by Adrian Dymorz over 10 years ago

I was accidentially using dbal extension. Uninstalling it solved the issues then.

I would agree to close this issue, because the documentation of dbal [1] says: "This means, not every aspect has been thoroughly checked" This probably is or was one of the aspects not checked.

[1] http://docs.typo3.org/typo3cms/extensions/dbal/Introduction/Index.html

Actions #6

Updated by Alexander Opitz over 10 years ago

  • Status changed from Needs Feedback to Closed

Thanks for feedback

Actions

Also available in: Atom PDF