Thread Details
  • State Not Answered
  • Replies 3 replies
  • Subscribers 353 subscribers
  • Views 615 views
  • Users 0 members are here
Forum Actions
Related

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

James Banbury

Hi team, 

We're stuck on the final stage of an upgrade whereby the upgrade script wants to create an index table:

Error creating table: bcn1_buyer_carbon_nominations_bcn1_buyer_carbon_nominations_1_c
'idx_bcn1_buyer_carbon_nominations_bcn1_buyer_carbon_nominations_1_ida1_deleted' is too long


The max length for MySQL table names is 64. The module was built with Module Builder.

Rebuilding the module would be a huge task since it's hooked into Integration packages and PMSE.

Has anyone run into this issue before and managed to resolve it without much pain?

Thanks, James.

Parents
  • 0

    Hi ,

    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

Reply
  • 0

    Hi ,

    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

Children