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 (Moderator: Dave Greenberg) »
  • log_conn_id has changed after recreating triggers
Pages: [1]

Author Topic: log_conn_id has changed after recreating triggers  (Read 581 times)

CatorgHans

  • I post frequently
  • ***
  • Posts: 157
  • Karma: 5
  • CiviCRM version: 4.4
  • CMS version: drupal
log_conn_id has changed after recreating triggers
May 16, 2013, 08:11:00 am
I am using logging in a 4.1.6 CiviCRM.

I noticed it was not logging anymore after a backup. Somehow the Triggers where not available anymore.

I went to the Logging Settings, saw that Logging was (still) on, changed nothing and pressed saved.

After that the Triggers where restored, the Logging tables where still filled with the old values and new changes came in the Logging tables.

But...

The older changes do not appear in the Logging reports and on the Contact Profiles.

I found out that the new changes now had a different log_conn_id then the old changes and that the reports use it in  their WHERE statements.

Question 1: What is log_conn_id for?
Question 2: Can I somehow see the old changes in the reports?

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: log_conn_id has changed after recreating triggers
May 16, 2013, 10:08:37 am

hey hans:

log_conn_id is a unique connection id string that mysql generates. This should be different for different connections and i think the reports use it sometime to group all updates that happened in the same transaction

this should not affect the reports, so seems like a bug/wierd thing. can u check the query generated by the reports

note that the logging reports will be super slow since the tables by default are archive and are not optimized. We dont expect folks to use those reports too often :)

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

CatorgHans

  • I post frequently
  • ***
  • Posts: 157
  • Karma: 5
  • CiviCRM version: 4.4
  • CMS version: drupal
Re: log_conn_id has changed after recreating triggers
May 16, 2013, 11:41:03 am
yeah, I know :)
I'll come back with some improvements.

One teaser: remove the trigger for civicrm_setting, a crazy amount of useless data is being stored.

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: log_conn_id has changed after recreating triggers
May 16, 2013, 12:19:00 pm
hey hans:

can u file a issue for skipping civicrm_setting. there are a few other tables we've discovered with nyss that we should not attach the triggers too (primarily mailing_event tables)

i'll add those skip clauses to 4.3.4

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 (Moderator: Dave Greenberg) »
  • log_conn_id has changed after recreating triggers

This forum was archived on 2017-11-26.