[ https://issues.apache.org/jira/browse/OFBIZ-5426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17051334#comment-17051334 ]
Pierre Smits edited comment on OFBIZ-5426 at 3/4/20, 3:38 PM: -------------------------------------------------------------- [~deepak], I presume the PR tested successfully (without flaws)... If so, current PR should be *good enough* to have it merged. And the suggestion can be taken into account the next time around. was (Author: pfm.smits): @deepak, I presume the PR tested successfully (without flaws)... If so, current PR should be *good enough* to have it merged. And the suggestion can be taken into account the next time around. > 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, > OFBIZ-5426.patch, OFBIZ-5426.patch > > Time Spent: 10m > Remaining Estimate: 0h > > 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)