You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ofbiz.apache.org by "Pawan Verma (JIRA)" <ji...@apache.org> on 2019/04/11 09:01:00 UTC
[jira] [Commented] (OFBIZ-5426) mysql: ERROR 1071 (42000):
Specified key was too long; max key length is 767 bytes
[ https://issues.apache.org/jira/browse/OFBIZ-5426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16815224#comment-16815224 ]
Pawan Verma commented on OFBIZ-5426:
------------------------------------
Attaching patch for the task.
Patch contains:
# Entity Name change
# Related Changes for the entity name change
# Migration service
I will update the Migration document when the changes committed into the repository.
Please let me know if any modification or correction is needed.
> mysql: ERROR 1071 (42000): Specified key was too long; max key length is 767 bytes
> ----------------------------------------------------------------------------------
>
> Key: OFBIZ-5426
> URL: https://issues.apache.org/jira/browse/OFBIZ-5426
> Project: OFBiz
> Issue Type: Bug
> Components: framework
> Affects Versions: Trunk
> Reporter: Leon
> Assignee: Pawan Verma
> Priority: Major
> Attachments: OFBIZ-5426.patch, OFBIZ-5426.patch
>
>
> Due to revision 1529838, the length of data type "email" was increased from 254 to 320. But It makes the ofbiz failed to create tables such as "PRODUCT_PROMO_CODE_EMAIL" which includes an email fields as its primary key.
> The database is mysql, innodb engine and utf8 charset. The error msg:
> ERROR 1071 (42000): Specified key was too long; max key length is 767 bytes.
> I suggest to revert change of r1529838.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)