[
https://issues.apache.org/jira/browse/OFBIZ-5426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17035397#comment-17035397
]
Pierre Smits commented on OFBIZ-5426:
-------------------------------------
It seems to me that, given that this ticket was created in 2013, it is
applicable to the active release branches (as well as past release branches and
releases). The 'Affects Version(s) field should reflect that, as this
information is not only valuable to contributors, but also adopters working
with implementations on those (past) branches and releases.
See also:
https://cwiki.apache.org/confluence/display/OFBIZ/Guidelines+For+Using+JIRA
> 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: Deepak Dixit
> Priority: Major
> Attachments: OFBIZ-5426.patch, 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
(v8.3.4#803005)
