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) »
  • db Upgrades and civicrm_activity_history
Pages: 1 [2]

Author Topic: db Upgrades and civicrm_activity_history  (Read 6261 times)

Deepak Srivastava

  • Moderator
  • Ask me questions
  • *****
  • Posts: 677
  • Karma: 65
Re: db Upgrades and civicrm_activity_history
May 07, 2008, 07:11:11 am
Quote from: davej on May 07, 2008, 05:07:21 am
There's another issue with activity history. In 1.9, there seem to be 2 civicrm_activity_history records per activity: one with entity_id = source and the other with entity_id = target and no indication in the db AFAICS of which is which, except that the record for the source seems to have been inserted first and so have a lower id. The 1.8/1.9 activity display code is clever enough to work out which is which and show the correct contacts as 'With Contact' and 'Created By'.

The 2.0.3 code doesn't handle this and instead displays two rows for a single activity.

Activity-history and other history tables /records are native to versions <= 1.9. And therefore work properly /w 1.8/1.9. I see this more as a 1.9 & 2.0 activity-compatibility-issue.
And AFA duplicate records are concerned i think it's safe to have duplicate records than risking dropping any of them. Since the rule might not work /w all kinds of history records.

(It would have been really appreciable, if such kind of issues were raised during design.)
« Last Edit: May 07, 2008, 07:46:56 am by Deepak Srivastava »
Found this reply helpful? Contribute NOW and help us improve CiviCRM with the Make it Happen! initiative.

FatherShawn

  • Ask me questions
  • ****
  • Posts: 372
  • Karma: 25
    • C3 Design
  • CiviCRM version: 4.2.11
  • CMS version: Drupal 7.23
  • MySQL version: 5.5.32
  • PHP version: 5.3.10
Re: db Upgrades and civicrm_activity_history
May 07, 2008, 09:10:08 am
Quote
Had you created an option in civicrm_option_value table you would see it in recipient's history too (this i just confirmed).


Well, that's good for the project as a whole.  As I said, there was not any critical data here for our organization.

In the interest of improving our service, I think that the data migration here needs to be more carefully thought out.  If the values for core functions in a table like civicrm_option_value are changed, then the upgrade process needs to change them to the expected value for the new version.  My impression from this discussion is that this must have happened prior to 1.9. Someone else who has upgraded through other versions and really needs that data should be able to upgrade and keep data generated by civiCRM core without a lot of extra work.  Otherwise we are contributing to the "CiviCRM is scary" perceptions...
Lead Developer, C3 Design.
Twitter: @FatherShawn
Pages: 1 [2]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Upgrading CiviCRM (Moderator: Deepak Srivastava) »
  • db Upgrades and civicrm_activity_history

This forum was archived on 2017-11-26.