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 Core CiviCRM Functions (Moderator: Yashodha Chaku) »
  • Merging under 3.3
Pages: [1]

Author Topic: Merging under 3.3  (Read 412 times)

krankie

  • I’m new here
  • *
  • Posts: 22
  • Karma: 2
  • CiviCRM version: 3.3.5
  • CMS version: Joomla! 1.5.22
  • MySQL version: 5.0.22-log
  • PHP version: 5.2.11
Merging under 3.3
January 04, 2011, 02:19:21 pm
I've just recently upgraded to 3.3 from 3.1.4 and performed some merges tonight for the first time.

I failed to notice the 'add new' box next to memberships and am worried that I may have lost some active memberships and retained some pending ones by failing to tick this box to keep both for post-merge inspection as I used to do.

I have a daily mysqldump backup (yay) so can use this to inspect the original records but first I need to find them again.  A search for changes done today is failing through the main interface (i think it is timing out) so I want to run a manual SQL query.

However I can't find where the change log date is stored on the civi database structure.  Can someone point me in the right direction please (or suggest a better approach if you have one).

Dave Greenberg

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 5760
  • Karma: 226
    • My CiviCRM Blog
Re: Merging under 3.3
January 05, 2011, 03:52:25 pm
If you've enabled the new 3.3 "Logging" feature (Configure > Global Settings > Misc Settings) then you'll have a set of tables that log all changes - table names are start with log_civicrm_*. and all have a log_date column.

Otherwise, change date + record id are written to civicrm_log table. modified_date column stores the date and time of the insert or update.
HTH
Protect your investment in CiviCRM by  becoming a Member!

krankie

  • I’m new here
  • *
  • Posts: 22
  • Karma: 2
  • CiviCRM version: 3.3.5
  • CMS version: Joomla! 1.5.22
  • MySQL version: 5.0.22-log
  • PHP version: 5.2.11
Re: Merging under 3.3
January 05, 2011, 04:31:47 pm
Thanks for this.

I don't have logging enabled yet, tried to do that on installing the upgrade but got an error - I think I may need to grant the mysql user extra permissions but haven't checked the error log yet.

In the meantime I discovered about two hours ago the new "Trash Contact" feature with this upgrade (I was several versions behind) so have managed to get the list of potentially affected members from that as all the dropped members from the merges were in there.

Tomorrow nights task will be to reload the live mysqldump from a few days ago into my test region and I can then browse them all manually - only about 12 affected I reckon.

Next time I'll be more careful to understand what features have changed between versions.   ::)

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using Core CiviCRM Functions (Moderator: Yashodha Chaku) »
  • Merging under 3.3

This forum was archived on 2017-11-26.