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) »
  • Changes in Schema Between 3.2 and 3.4.8 - How to deal with them?
Pages: [1]

Author Topic: Changes in Schema Between 3.2 and 3.4.8 - How to deal with them?  (Read 1096 times)

SWD

  • I’m new here
  • *
  • Posts: 19
  • Karma: 0
  • CiviCRM version: 3.4.8
  • CMS version: Drupal 6.22
  • MySQL version: 5.5.20
  • PHP version: 5.3.9
Changes in Schema Between 3.2 and 3.4.8 - How to deal with them?
December 19, 2011, 10:41:59 pm
Hi everyone,
I am currently in the middle of my first ever experience with CiviCRM.  I think it's fair to say it's been quite the experience to date.   We've got a bit of a double whammy scenario in that we are not only migrating from one server to another but we are also trying to upgrade to the latest version of CiviCRM for Drupal 6.22. 

After quite the battle initially I decided to follow the migration guide on this site.  It recommended a fresh installation of CiviCRM.  This initially seemed to go quite while but now I am trying to load in the data from the CiviCRM 3.2 database and finding that the database structure has changed quite considerably.   There are both new fields added plus numerous fields have been dropped.

What I'm wondering is if someone can offer a suggestion on how we should deal with these structural differences.  Should I temporarily reinstate columns that have been dropped between 3.2 and 3.4.8 and then drop them once I have imported all the data or is it possible that I will likely have issues with lost data and the like.

Play devils advocate for a moment.  If someone is reading this and is just thinking no, no, no, he's gone about it all the wrong way can you please post a recommended approach for this scenario.    I wish we could just do the upgrade but sadly due to issues with our client's current host we have to both migrate and upgrade.

Any help would be really appreciated.
Thanks
Josh

Erik Hommel

  • Forum Godess / God
  • I live on this forum
  • *****
  • Posts: 1773
  • Karma: 59
    • EE-atWork
  • CiviCRM version: all sorts
  • CMS version: Drupal
  • MySQL version: Ubuntu's latest LTS version
  • PHP version: Ubuntu's latest LTS version
Re: Changes in Schema Between 3.2 and 3.4.8 - How to deal with them?
December 19, 2011, 11:01:12 pm
Hmmm challenging scenario! From what version are you upgrading? Can you identify what data you exactly need in your updated install? Is it a possibility to just install a new CiviCRM and use the import functionality to get the data in? Or even develop some migration script? That obviously depends on how much of the CiviCRM modules (and data) you use....
Consultant/project manager at EEatWork and CiviCooP (http://www.civicoop.org/)

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: Changes in Schema Between 3.2 and 3.4.8 - How to deal with them?
December 19, 2011, 11:32:23 pm

if you have the 3.2 DB, why dont u install the 3.4.8 code and then run the civicrm upgrade url (q=civicrm/upgrade&reset=1)

u need to be logged into drupal as an admin

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

Hershel

  • Forum Godess / God
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4640
  • Karma: 176
    • CiviHosting
  • CiviCRM version: Latest
  • CMS version: Mostly WordPress and Drupal
Re: Changes in Schema Between 3.2 and 3.4.8 - How to deal with them?
December 20, 2011, 02:39:06 am
Quote from: SWD on December 19, 2011, 10:41:59 pm
I wish we could just do the upgrade but sadly due to issues with our client's current host we have to both migrate and upgrade.

Why? If you have access to the DB, so empty it and put in your old DB and then upgrade. Or run the upgrade on another machine, like your own workstation, and then import the full DB into the live DB.
CiviHosting and CiviOnline -- The CiviCRM hosting experts, since 2007

See here for the official: What to do if you think you've found a bug.

SWD

  • I’m new here
  • *
  • Posts: 19
  • Karma: 0
  • CiviCRM version: 3.4.8
  • CMS version: Drupal 6.22
  • MySQL version: 5.5.20
  • PHP version: 5.3.9
Re: Changes in Schema Between 3.2 and 3.4.8 - How to deal with them?
December 20, 2011, 03:40:00 pm
Thanks everyone.  I guess your responses show my inexperience with the system!  Am attempting your suggested approach now.  Will report back once I'm done!

Thanks again for taking the time to respond.
Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Upgrading CiviCRM (Moderator: Deepak Srivastava) »
  • Changes in Schema Between 3.2 and 3.4.8 - How to deal with them?

This forum was archived on 2017-11-26.