CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site
This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Upgrading CiviCRM (Moderator: Deepak Srivastava) »
  • database upgrade issue due to long custom data table name
Pages: [1]

Author Topic: database upgrade issue due to long custom data table name  (Read 462 times)

davesage

  • I post frequently
  • ***
  • Posts: 153
  • Karma: 3
  • CiviCRM version: 3.4 & 4.1
  • CMS version: Joomla 1.5 & 2.5
  • MySQL version: 5.1
  • PHP version: 5.3
database upgrade issue due to long custom data table name
October 07, 2013, 07:21:11 pm
Hi,

Did an upgrade tonight and had an error when trying to update the database. when I dug a bit deeper I found that the issue was with a long table name for a custom data field table - 'civicrm_value_craft_fair_registration_information_10' the upgrade script couldn't drop a trigger or something.

I altered the the table name to make it shorter and it worked. Changed the reference in civicrm_custom_group and it looks as though all is well.

Do you think the system should restrict the length of the text input field when creating a custom data set in order to ensure that this error does not occur? Can anyone let me know what the length is that this error occurs with?

Just thought I should raise it to help others not face an upgrade error in future.

Thanks,

Dave

Chris Burgess

  • Ask me questions
  • ****
  • Posts: 675
  • Karma: 59
Re: database upgrade issue due to long custom data table name
October 07, 2013, 08:20:11 pm
There is an upgrade test suite, to identify upgrade issues - it would be worthwhile contributing a test for longer table names to that test so the case can be handled.

https://github.com/civicrm/civicrm-upgrade-test

It would also be a good idea to limit table name size (eg if we need to be able to prepend "civicrm_temporary", then we need to account for that many letters, etc etc).
@xurizaemon ● www.fuzion.co.nz

Donald Lobo

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 15963
  • Karma: 470
    • CiviCRM site
  • CiviCRM version: 4.2+
  • CMS version: Drupal 7, Joomla 2.5+
  • MySQL version: 5.5.x
  • PHP version: 5.4.x
Re: database upgrade issue due to long custom data table name
October 08, 2013, 12:56:27 am

There is a known bug with regard to long trigger names. Unfortunately no one has submitted a patch for this as yet

can you take a look and contribute a patch?

lobo
A new CiviCRM Q&A resource needs YOUR help to get started. Visit our StackExchange proposed site, sign up and vote on 5 questions
Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Upgrading CiviCRM (Moderator: Deepak Srivastava) »
  • database upgrade issue due to long custom data table name

This forum was archived on 2017-11-26.