Details
-
Type: Bug
-
Status: Done/Fixed
-
Priority: Trivial
-
Resolution: Duplicate
-
Affects Version/s: 4.3.3
-
Fix Version/s: 4.6
-
Component/s: Core CiviCRM
-
Labels:None
Description
The end-user created a new custom field set that they named "High Holy Day Services Ticket Registration" . CiviCRM then created a new MySQL table called "civicrm_value_high_holy_day_services_ticket_registration_67"
In the short term, this worked as the end-user was able to add various custom fields to the set and use it to store data. However, when the end-user tried to edit any of the custom fields in this set, clicking "Save" produced the following SQL error:
"DROP TRIGGER IF EXISTS civicrm_value_high_holy_day_services_ticket_registration_67_before_insert [nativecode=1059 ** Identifier name 'civicrm_value_high_holy_day_services_ticket_registration_67_before_insert' is too long]
I was able to work-around the issue in my environment by renaming the table to a shorter name, and also updating the corresponding table name value in "civicrm_custom_group". But it seems that the CiviCRM-generated table name should never be allowed to be that long, no matter what the end-user does.