11.0.6 Upgrade failed: (Creating an index table name which is too long!)

RE: 11.0.6 Upgrade failed: (Creating an index table name which is too long!)

James Banbury — Fri, 14 Apr 2023 10:13:47 GMT

Hi Francesca Shiekh thank you for your input, very useful!
It's a shame SugarCRM has not released a patch sooner as "bcn1_buyer_carbon_nominations" is not an incredibly large module name, although a lesson learnt to keep them short from now onwards.

RE: 11.0.6 Upgrade failed: (Creating an index table name which is too long!)

Rodrigo Manara — Fri, 14 Apr 2023 07:52:02 GMT

Francesca Shiekh I will try this and let you know.

RE: 11.0.6 Upgrade failed: (Creating an index table name which is too long!)

Francesca Shiekh — Thu, 13 Apr 2023 16:27:08 GMT

Hi James Banbury,

I had this issue on multiple indexes on many of my custom modules that were added since v6.x

I think it first popped up when we moved to MySQL 8.0.x

Possibly not the cleanest solution, but... I did a grep for the index names in my code and shortened each one in a consistent manner to make them fit. I had quite a few of those.

At that same time we also had problems with the INT fields reporting a mismatch when doing a QRR, but not really doing anything when executing the prompted SQL. https://portal.sugarondemand.com/#supp_Bugs/87739
I believe that bug is fixed in v13, but you will need a Hotfix for v11 and another for v12 if you want to get rid of the mismatch notification when you QRR.

FrancescaS