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) »
  • 1.9 to 2.0Beta2 and Joomla
Pages: [1]

Author Topic: 1.9 to 2.0Beta2 and Joomla  (Read 1907 times)

montano

  • Guest
1.9 to 2.0Beta2 and Joomla
February 26, 2008, 01:56:05 pm
The original installation was 1.9.  I am attempting to upgrade to 2.0 beta 2 and got through most of the steps when this occurred in step 5
Code: [Select]
Error Details:

Array
(
    [callback] => Array
        (
            [0] => CRM_Core_Error
            [1] => handle
        )

    [code] => -1
    [message] => DB Error: unknown error
    [mode] => 16
    [debug_info] =>         ALTER TABLE custom_value_1_Custom_Contact_Information
        ADD COLUMN `ID` varchar(255),
        ADD INDEX INDEX_ID ( ID ) [nativecode=1060 ** Duplicate column name 'ID']
    [type] => DB_Error
    [user_info] =>         ALTER TABLE custom_value_1_Custom_Contact_Information
        ADD COLUMN `ID` varchar(255),
        ADD INDEX INDEX_ID ( ID ) [nativecode=1060 ** Duplicate column name 'ID']
    [to_string] => [db_error: message="DB Error: unknown error" code=-1 mode=callback callback=CRM_Core_Error::handle prefix="" info="        ALTER TABLE custom_value_1_Custom_Contact_Information
        ADD COLUMN `ID` varchar(255),
        ADD INDEX INDEX_ID ( ID ) [nativecode=1060 ** Duplicate column name 'ID']"]
[/code]

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: 1.9 to 2.0Beta2 and Joomla
February 26, 2008, 02:06:56 pm

you have a custom field called id in v1.9. the short term fix is to rename that custom field to something else (like myID) so it does not conflict with our auto created id. we'll add this as a verification step and also disallow this in 2.0

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

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Upgrading CiviCRM (Moderator: Deepak Srivastava) »
  • 1.9 to 2.0Beta2 and Joomla

This forum was archived on 2017-11-26.