Re: PEAR::Translation2 bug with MySQL when adding new language.
| From: | Lorenzo Alberton | Date: | Wed, 22 Feb 2006 16:22:47 +0000 |
| Subject: | Re: PEAR::Translation2 bug with MySQL when adding new language. | ||
| References: | 1 | Groups: | php.pear.general |
| Request: | Send a blank email to pear-general+get-23092@lists.php.net to get a copy of this message | ||
Hi AJ,
When I add a new language using the PEAR::DB container I get this error CREATE UNIQUE INDEX translation_en_iso_8859_15_translation_id_index ON translation_en_iso_8859_15 (translation_id) [nativecode=1170 ** BLOB/TEXT column 'translation_id' used in key specification without a key length] I'm using MySQL 4.1.13 on SuSE linux. According to MySQL's manual when creating a unique index on a column with the type 'TEXT' you need to specify a length. So the query for MySQL should bemany thanks for the report. I've updated the files in CVS; now I'm going through a few more tweaks, then I'll roll out a new release, hopefully today. Stay tuned... Cheers, -- Lorenzo Alberton http://pear.php.net/user/quipo