MySQL Error 1170 (42000): BLOB/TEXT Column Used in Key Specification Without a Key Length
When creating a new table or altering an existing table with primary keys, unique constraints and indexes, or when defining a new index with Alter Table manipulation statement in MySQL database, the following error may occur and prohibit the the command from completing:
ERROR 1170 (42000): BLOB/TEXT column ‘field_name’ used in key specification without a key length
The error happens because MySQL can index only the first N chars of a BLOB or TEXT column. So The error mainly happen when there is a field/column type of TEXT or BLOB or those belongs to TEXT or BLOB types such as TINYBLOB, MEDIUMBLOB, LONGBLOB, TINYTEXT, MEDIUMTEXT, and LONGTEXT that you try to make as primary key or index. With full BLOB or TEXT without the length value, MySQL is unable to guarantee the uniqueness of the column as it’s of variable and dynamic size. So, when using BLOB or TEXT types as index, the value of N must be supplied so that MySQL can determine the key length. However, MySQL doesn’t support limit on TEXT or BLOB. TEXT(88) simply won’t work.
The error will also pop up when you try to convert a table column from non-TEXT and non-BLOB type such as VARCHAR and ENUM into TEXT or BLOB type, with the column already been defined as unique constraints or index. The Alter Table SQL command will fail.
The solution to the problem is to remove the TEXT or BLOB column from the index or unique constraint, or set another field as primary key. If you can’t do that, and wanting to place a limit on the TEXT or BLOB column, try to use VARCHAR type and place a limit of length on it. By default, VARCHAR is limited to a maximum of 255 characters and its limit must be specified implicitly within a bracket right after its declaration, i.e VARCHAR(200) will limit it to 200 characters long only.
Sometimes, even though you don’t use TEXT or BLOB related type in your table, the Error 1170 may also appear. It happens in situation such as when you specify VARCHAR column as primary key, but wrongly set its length or characters size. VARCHAR can only accepts up to 256 characters, so anything such as VARCHAR(512) will force MySQL to auto-convert the VARCHAR(512) to a SMALLTEXT datatype, which subsequently fail with error 1170 on key length if the column is used as primary key or unique or non-unique index. To solve this problem, specify a figure less than 256 as the size for VARCHAR field.
Related Articles
- How to Find and Replace Text in MySQL Database using SQL
- WordPress MySQL SQL Query Error in WPDB Class
- Change and Reset MySQL root Password
- Text Copying Disabled (Fix Copy and Paste Not Working Error)
- Adding Extra More Fields to WordPress Write/Edit Post/Page Right Column
- Remove or Trim First or Last Few Characters in MySQL Database with SQL
- Installing Web Server in FreeBSD 6.0 with Apache 2.2, MySQL 5.0 and PHP 5 – Part 3
- MySQL Database Performance Tuning Best Practices Video Tutorial
- Check and Optimize MySQL Database Automatically with Crontab/Cron
- Enable MySQL InnoDB Storage Engine Support in XAMPP Installation










































April 30th, 2009 22:32
Thank you for the post.
I need a key that is longer then 256.
What can I do?
googling it for the past 3 hours with no luck…
(Paco Zarabozo comment did not work for me)
December 13th, 2008 22:20
[...] I ran into some problems, I back-pedalled to square one. Thankfully my backup restored the Latin1 database without any [...]
October 29th, 2008 10:16
Well, here’s another solution. You can actually specify the key length for your index while keeping your field as longtext. This is an example:
create table messages (
id int(20) not null auto_increment,
message longtext,
index (message(996), id)
);
desc messages;
show index from messages;
996 is the maximium key length mySQL has accepted for me.
Cheers,
Paco
October 27th, 2008 19:50
Thanks a lot!
October 6th, 2008 03:50
Thank you very much. I had this problem and you were a life saver!
March 7th, 2008 04:15
Thanks, very good defined
February 23rd, 2008 03:40
Thanks for the post. Very helpful.
February 20th, 2008 02:45
Thanks! Very useful post.
August 30th, 2007 18:33
Thanks for putting this up. I didn’t get the error and you saved me a lot o frustration. I’d put you in the ‘Goog people’ category anytime