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 »
  • Using CiviCRM »
  • Using CiviEvent (Moderator: Yashodha Chaku) »
  • Export Participants DB Err: Row size too large. The maximum row size for the use
Pages: [1]

Author Topic: Export Participants DB Err: Row size too large. The maximum row size for the use  (Read 1584 times)

elmobile

  • I’m new here
  • *
  • Posts: 13
  • Karma: 0
    • elMobile Inc.
  • CiviCRM version: 3.1, 3.3, 3.4, 4.1
  • CMS version: Drupal 6.16, 6.22, 7 / Joomla 1.5, 2.5
Export Participants DB Err: Row size too large. The maximum row size for the use
October 12, 2011, 12:06:15 pm
I have a CiviCRM upgraded from v 3.1.3/Drupal v6.16 to v3.4.6/Drupal v6.22 following the upgrade instructions.
All 250 custom fields of one Participant are kept in the v3.4.6.
I can see the field values of each Participant from CiviEvent v3.4.6.

When I tried to Export Participants from an Event, after selecting
Export PRIMARY fields
in Step 2 of 3 during Export Participants,
CiviCRM throws a DB error:

Database Error Code: Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535. You have to change some columns to TEXT or BLOBs, 1118

Detail list of errors are attached.

For CiviCRM v3.1.3, Export Participants worked perfectly.

Did we miss anything during the upgrade?

Thanks for you comments.

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: Export Participants DB Err: Row size too large. The maximum row size for the use
October 12, 2011, 01:37:53 pm

yes, we changed the export and use a temp table to store the results for efficiency and memory reasons

250 custom fields seems a bit too much :( This is a bit of an edge case for the code to deal with

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

elmobile

  • I’m new here
  • *
  • Posts: 13
  • Karma: 0
    • elMobile Inc.
  • CiviCRM version: 3.1, 3.3, 3.4, 4.1
  • CMS version: Drupal 6.16, 6.22, 7 / Joomla 1.5, 2.5
Re: Export Participants DB Err: Row size too large. The maximum row size for the use
October 12, 2011, 07:11:22 pm
The reason why we upgrade from v3.1.3 to v3.4.6 is to use the nice user interface for the mass Email feature: schedule a newsletter, select a template with opt-out link, test it, and send respectfully.

In v3.1.3 the event admin has to manually email at most 50 participants at a time.
That could be automated by the mass Email in v3.4.6.

Would v3.3.x provide similar mass Email scheduler and the Export Participants with 250 custom fields work?

The custom fields are of a master template covering event registration with minors under guardian's name and related wellness attributes.

Any pointer appreciated!

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: Export Participants DB Err: Row size too large. The maximum row size for the use
October 12, 2011, 07:49:14 pm

no. the export fix was introduced in 3.3.x

your best bet would be to reduce the number of custom fields down to a more reasonable size

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

elmobile

  • I’m new here
  • *
  • Posts: 13
  • Karma: 0
    • elMobile Inc.
  • CiviCRM version: 3.1, 3.3, 3.4, 4.1
  • CMS version: Drupal 6.16, 6.22, 7 / Joomla 1.5, 2.5
Re: Export Participants DB Err: Row size too large. The maximum row size for the use
October 13, 2011, 07:39:14 pm
The following test is on v3.4.6 --

I've made different Custom Field Groups and associated each with different Event Type,
say, Custom Field Group A for Event Type A and Custom Field Group B for Event Type B.
Am following the User Guide at
http://en.flossmanuals.net/civicrm/organising-your-data/extending-core-data/

When I Export Participants with the option,
Export PRIMARY fields,
checked,
The output CSV file for Event Type A has both Custom Field Group A *and* Custom Field Group B.
Same problem in the CSV file for Event Type B:
both Custom Field Group A *and* Custom Field Group B exist for Participants associated with Custom Field Group B only.

How can I Export Participants with associated Custom Field Groups only?

The 'super-set' of all Participant related Custom Field Groups will exceed the DB limit
and trigger the 'Row size too large' error during Export Participants.

Please help!

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: Export Participants DB Err: Row size too large. The maximum row size for the use
October 14, 2011, 09:35:19 am

you'll need to choose the second option (select fields for export) and save that mapping. However i'm not sure how many fields it allows you to choose

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 »
  • Using CiviCRM »
  • Using CiviEvent (Moderator: Yashodha Chaku) »
  • Export Participants DB Err: Row size too large. The maximum row size for the use

This forum was archived on 2017-11-26.