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) »
  • civicrm export participants throwing SQL error
Pages: [1]

Author Topic: civicrm export participants throwing SQL error  (Read 362 times)

riswana123

  • I’m new here
  • *
  • Posts: 5
  • Karma: 0
  • CiviCRM version: 3.4.6
  • CMS version: Drupal 6
  • MySQL version: 5.3
  • PHP version: 5.5
civicrm export participants throwing SQL error
November 27, 2013, 09:18:10 pm
Hi everyone,
           While exporting event participants i am getting  sql error "Can not join more than 61 tables".  I am having more custom tables. How to resolve this issue?

CiviTeacher.com

  • I live on this forum
  • *****
  • Posts: 1282
  • Karma: 118
    • CiviTeacher
  • CiviCRM version: 3.4 - 4.5
  • CMS version: Drupal 6&7, Wordpress
  • MySQL version: 5.1 - 5.5
  • PHP version: 5.2 - 5.4
Re: civicrm export participants throwing SQL error
December 04, 2013, 09:04:02 am
61 joins is a hard limit enforced by MySQL database language.  That said, if you are joining this many custom tables on an export, then congratulations to you for having the most custom data tables I have ever heard of!  ;D

I suggest breaking your export into two steps, exporting a few dozen tables, and then a few dozen more.  sort each exported file by participant_id and then copy and paste the tables together if the rows match up
Try CiviTeacher: the online video tutorial CiviCRM learning library.

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviEvent (Moderator: Yashodha Chaku) »
  • civicrm export participants throwing SQL error

This forum was archived on 2017-11-26.