Support (offered by community volunteers) > Upgrading CiviCRM

Updating the database along with module upgrade - Which documenation to follow?

(1/1)

bsharp222:
I am trying to update the database schema to be compatible for my 2.2 to 3.0 CiviCRM upgrade.  I am getting errors, and I have two lurking questions.

1. Should I be using the current documentation instructions, or should I use the documentation for 3.0?  I've been using the civicrm.mysql file that comes tarred with 3.0.4.
http://wiki.civicrm.org/confluence/display/CRMDOC30/Ensuring+Schema+Integrity+on+Upgrades [nofollow]
http://wiki.civicrm.org/confluence/display/CRMDOC41/Ensuring+Schema+Integrity+on+Upgrades [nofollow]

Also, it seems like the instructions are pretty much the same, but the older documentation doesn't get into the details of how to do it yourself.  Are the steps different?  Using the 4.1 instructions with the 3.0 civicrm.mysql file, I get the following errors during the step where I give MySQL the data.sql file:

ERROR 1054 (42S22): Unknown column 'due_date_time' in 'field list'
ERROR 1054 (42S22): Unknown column 'greeting_type_id' in 'field list'
ERROR 1054 (42S22): Unknown column 'default_discount_id' in 'field list'
ERROR 1054 (42S22): Unknown column 'location_count' in 'field list'


2. I create a new database through DreamHost's web panel, and I am not sure if there is a way to change the configuration for it.  After feeding the files into MySQL, I look at the default storage engine in phpMyAdmin.  Even though I have set the variable to InnoDB prior to feeding MySQL the files, the database still uses MyISAM as the default engine.  The tables are all InnoDB, but the database itself doesn't seem to be.  I can't change the configuration file (my.cnf) for MySQL.  The server runs Ver 14.12 Distrib 5.0.51a of MySQL.  I feel like it being stored as MyISAM will cause a complication that I have seen others face in the forum around foreign key constraints.  Is it worth getting the default store engine changed to InnoDB?

I don't know what is causing my errors, but I am at my wit's end.  I have done my best not to rely on asking a lot of questions.  Fortunately I found a lot of the mistakes I was making along the way.  If I can't proceed any further then a specialist will have to be hired in to help.

Doug MB:
Were you able to resolve your issue?

Hershel:
Hi. You should use the old instructions because the upgrade procedure has changed over the years.

The default table engine being MyISAM or InnoDB makes no difference--as long as InnoDB is enabled that's all you need.

Regarding your "Unknown column" errors, what file exactly are you importing to get this error?

bsharp222:
I resolved the issue, but unfortunately I don't recall the steps.  I went from 2.2 to 3.4 to 4.1.  I'm working on the site again after things got all settled in.  I'll share the solution if I find it in my notes.

Thanks for responding, having forum support is invaluable.

Navigation

[0] Message Index