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) »
  • How is 3.4.1 stability / bug free wise? Considering upgrading from 3.3.6
Pages: 1 [2]

Author Topic: How is 3.4.1 stability / bug free wise? Considering upgrading from 3.3.6  (Read 1890 times)

Hershel

  • Forum Godess / God
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4640
  • Karma: 176
    • CiviHosting
  • CiviCRM version: Latest
  • CMS version: Mostly WordPress and Drupal
Re: How is 3.4.1 stability / bug free wise? Considering upgrading from 3.3.6
June 30, 2011, 03:20:19 am
Quote from: Eileen on June 30, 2011, 03:17:22 am
I generally do a Civi only backup using backup migrate right before I upgrade so it I have to restore Civi only

But what if the update created new tables? Then those my be removed by hand, no?

With a separate database, I just DROP it and then CREATE it fresh and then import the backup.
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.

Eileen

  • Forum Godess / God
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4195
  • Karma: 218
    • Fuzion
Re: How is 3.4.1 stability / bug free wise? Considering upgrading from 3.3.6
June 30, 2011, 03:32:27 am
Yes, I guess I have hit that - there are a few suggestions out there on how to do essentially 'drop table like civicrm_%'

http://dev.mysql.com/doc/refman/5.5/en/drop-table.html

But you are right - it can be a gotcha
Make today the day you step up to support CiviCRM and all the amazing organisations that are using it to improve our world - http://civicrm.org/contribute

xavier

  • Forum Godess / God
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4453
  • Karma: 161
    • Tech To The People
  • CiviCRM version: yes probably
  • CMS version: drupal
Re: How is 3.4.1 stability / bug free wise? Considering upgrading from 3.3.6
June 30, 2011, 04:35:36 am
Hi,

I recently upgraded an install of dolibarr (a kind of ERP) that was years old. They have managed to have the upgrade script being able to run several time without crashing on tables that already exists.

Probably means quite a lot of extra tests, but adding a DROP table IF EXISTS before the create ones in the upgrade sql would avoid this issue and shouldn't be too complicated, woudldn't it?

(I'll keep an eye on the sql upgrade to see if it could work)

X+
-Hackathon and data journalism about the European parliament 24-26 jan. Watch out the result

Eileen

  • Forum Godess / God
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4195
  • Karma: 218
    • Fuzion
Re: How is 3.4.1 stability / bug free wise? Considering upgrading from 3.3.6
June 30, 2011, 02:00:19 pm
Well, the script would be able to first analyse the DB compared to any tables fields or indexes it wants to add & then offer to proceed (drop & create) or not do the upgrade (preventing the DB screwed situation). Ideally if it would do it before it runs each point version. Realistically it would probably save us a lot of support time & the Civi community quite a bit of frustration.
Make today the day you step up to support CiviCRM and all the amazing organisations that are using it to improve our world - http://civicrm.org/contribute
Pages: 1 [2]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Upgrading CiviCRM (Moderator: Deepak Srivastava) »
  • How is 3.4.1 stability / bug free wise? Considering upgrading from 3.3.6

This forum was archived on 2017-11-26.