Re: Too many key parts specified; max 16 parts allowed
MyISAM's limit is the same as SQL Server's, 16 cols/key.
InnopDB limit is 3500 bytes/key, but if the table uses utf8mb4, that's only 3500/4=875 chars.
I've never seen a problem that required more than 16 cols in a key. Are you sure you need that?
Since 5.7.6 (getting near release), MySQL supports GENERATED columns that may reference built-in functions and may be VIRTUAL or STORED; if STORED, I think they can reference as many columns as you can fit in such a spec, so that might be a solution for you.
Subject
Views
Written By
Posted
9155
April 02, 2015 05:47AM
Re: Too many key parts specified; max 16 parts allowed
5070
April 02, 2015 11:06AM
3400
April 04, 2015 08:37PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.