3.4.4. > 3.4.5 upgrade fails with "Column 'weight' cannot be null, 1048"

[Slovak]

I had trouble with this specific site upgrading from 3.3.6 directly to 3.4.5 so I did incremental upgrades all the way to 3.4.4 without issues. Now going from 3.4.4. to 3.4.5 I receive the following error:

Code: [Select]

Database Error Code: Column 'weight' cannot be null, 1048
Additional Details:
Array
(
    [callback] => Array
        (
            [0] => CRM_Core_Error
            [1] => handle
        )

    [code] => -3
    [message] => DB Error: constraint violation
    [mode] => 16
    [debug_info] => INSERT INTO civicrm_option_value
  (option_group_id, is_default, is_active, name, value, label, weight)
VALUES
(@option_group_id_languages, 0, 1, 'de_CH', 'de', 'German (Swiss)', @counter := @counter + 1),
(@option_group_id_languages, 0, 1, 'es_PR', 'es', 'Spanish; Castilian (Puerto Rico)', @counter := @counter + 1) [nativecode=1048 ** Column 'weight' cannot be null]
    [type] => DB_Error
    [user_info] => INSERT INTO civicrm_option_value
  (option_group_id, is_default, is_active, name, value, label, weight)
VALUES
(@option_group_id_languages, 0, 1, 'de_CH', 'de', 'German (Swiss)', @counter := @counter + 1),
(@option_group_id_languages, 0, 1, 'es_PR', 'es', 'Spanish; Castilian (Puerto Rico)', @counter := @counter + 1) [nativecode=1048 ** Column 'weight' cannot be null]
    [to_string] => [db_error: message="DB Error: constraint violation" code=-3 mode=callback callback=CRM_Core_Error::handle prefix="" info="INSERT INTO civicrm_option_value
  (option_group_id, is_default, is_active, name, value, label, weight)
VALUES
(@option_group_id_languages, 0, 1, 'de_CH', 'de', 'German (Swiss)', @counter := @counter + 1),
(@option_group_id_languages, 0, 1, 'es_PR', 'es', 'Spanish; Castilian (Puerto Rico)', @counter := @counter + 1) [nativecode=1048 ** Column 'weight' cannot be null]"]
)

After restoring the db back to 3.4.4 backup, I have checked and confirmed that table civicrm_option_value contains no NULL values in the weight column.

Any other suggestions would be welcome.

[Kurund Jalmi]

It's a bug in upgrade hence filed: http://issues.civicrm.org/jira/browse/CRM-8619

Kurund

[Slovak]

Thanks Kurund. Is there a recommended upgrade path at the moment, or do I need to wait for 3.4.6 release?

[Kurund Jalmi]

For now you can get the patch from https://fisheye2.atlassian.com/changelog/CiviCRM?cs=35621 for 3.4.5

Kurund

[Slovak]

I applied the patch, and now get the following error (I've replaced the actual database name with db_name):

Code: [Select]

Database Error Code: Cannot add or update a child row: a foreign key constraint fails (`db_name`.`civicrm_option_value`, CONSTRAINT `FK_civicrm_option_value_option_group_id` FOREIGN KEY (`option_group_id`) REFERENCES `civicrm_option_group` (`id`) ON DELETE CASCADE), 1452
Additional Details:
Array
(
    [callback] => Array
        (
            [0] => CRM_Core_Error
            [1] => handle
        )

    [code] => -3
    [message] => DB Error: constraint violation
    [mode] => 16
    [debug_info] => INSERT INTO civicrm_option_value
  (option_group_id, is_default, is_active, name, value, label, weight)
VALUES
(@option_group_id_languages, 0, 1, 'de_CH', 'de', 'German (Swiss)', @weight := @languages_max_weight + 1),
(@option_group_id_languages, 0, 1, 'es_PR', 'es', 'Spanish; Castilian (Puerto Rico)', @weight := @languages_max_weight + 2) [nativecode=1452 ** Cannot add or update a child row: a foreign key constraint fails (`db_name`.`civicrm_option_value`, CONSTRAINT `FK_civicrm_option_value_option_group_id` FOREIGN KEY (`option_group_id`) REFERENCES `civicrm_option_group` (`id`) ON DELETE CASCADE)]
    [type] => DB_Error
    [user_info] => INSERT INTO civicrm_option_value
  (option_group_id, is_default, is_active, name, value, label, weight)
VALUES
(@option_group_id_languages, 0, 1, 'de_CH', 'de', 'German (Swiss)', @weight := @languages_max_weight + 1),
(@option_group_id_languages, 0, 1, 'es_PR', 'es', 'Spanish; Castilian (Puerto Rico)', @weight := @languages_max_weight + 2) [nativecode=1452 ** Cannot add or update a child row: a foreign key constraint fails (`db_name`.`civicrm_option_value`, CONSTRAINT `FK_civicrm_option_value_option_group_id` FOREIGN KEY (`option_group_id`) REFERENCES `civicrm_option_group` (`id`) ON DELETE CASCADE)]
    [to_string] => [db_error: message="DB Error: constraint violation" code=-3 mode=callback callback=CRM_Core_Error::handle prefix="" info="INSERT INTO civicrm_option_value
  (option_group_id, is_default, is_active, name, value, label, weight)
VALUES
(@option_group_id_languages, 0, 1, 'de_CH', 'de', 'German (Swiss)', @weight := @languages_max_weight + 1),
(@option_group_id_languages, 0, 1, 'es_PR', 'es', 'Spanish; Castilian (Puerto Rico)', @weight := @languages_max_weight + 2) [nativecode=1452 ** Cannot add or update a child row: a foreign key constraint fails (`db_name`.`civicrm_option_value`, CONSTRAINT `FK_civicrm_option_value_option_group_id` FOREIGN KEY (`option_group_id`) REFERENCES `civicrm_option_group` (`id`) ON DELETE CASCADE)]"]
)


[Kurund Jalmi]

Just to confirm, did you rollback to 3.4.4 and then tried upgrade? You can replace existing "3.4.5.mysql.tpl" with below file http://svn.civicrm.org/civicrm/branches/v4.0/CRM/Upgrade/Incremental/sql/3.4.5.mysql.tpl

HTh
Kurund

[Slovak]

Just to confirm, did you rollback to 3.4.4 and then tried upgrade?

Correct, I rolled back, even dropped all the tables then restored from backup to ensure I had nothing hanging loose.

You can replace existing "3.4.5.mysql.tpl" with below file http://svn.civicrm.org/civicrm/branches/v4.0/CRM/Upgrade/Incremental/sql/3.4.5.mysql.tpl

That file doesn't seem to have the same changes reflected as https://fisheye2.atlassian.com/changelog/CiviCRM?cs=35621

[Kurund Jalmi]

Sorry check this file

http://svn.civicrm.org/civicrm/branches/v3.4/CRM/Upgrade/Incremental/sql/3.4.5.mysql.tpl

Kurund

[Slovak]

Sorry check this file

http://svn.civicrm.org/civicrm/branches/v3.4/CRM/Upgrade/Incremental/sql/3.4.5.mysql.tpl

Kurund

That again appears to be the same file as included with the 3.4.5 distribution.

[Kurund Jalmi]

That again appears to be the same file as included with the 3.4.5 distribution.

Nope it's not, it contains code for collect weight calculation.

Kurund

[Slovak]

Nope it's not, it contains code for collect weight calculation.

My mistake, I must have pulled a different file. This one has upgraded successfully to 3.4.5. Thank you for your guidance.

[Slovak]

Getting the same error now on another site when upgrading from 4.0.4 to 4.0.5

Code: [Select]

Database Error Code: Column 'weight' cannot be null, 1048
Additional Details:
Array
(
    [callback] => Array
        (
            [0] => CRM_Core_Error
            [1] => handle
        )

    [code] => -3
    [message] => DB Error: constraint violation
    [mode] => 16
    [debug_info] => INSERT INTO civicrm_option_value
  (option_group_id, is_default, is_active, name, value, label, weight)
VALUES
(@option_group_id_languages, 0, 1, 'de_CH', 'de', 'German (Swiss)', @counter := @counter + 1),
(@option_group_id_languages, 0, 1, 'es_PR', 'es', 'Spanish; Castilian (Puerto Rico)', @counter := @counter + 1) [nativecode=1048 ** Column 'weight' cannot be null]
    [type] => DB_Error
    [user_info] => INSERT INTO civicrm_option_value
  (option_group_id, is_default, is_active, name, value, label, weight)
VALUES
(@option_group_id_languages, 0, 1, 'de_CH', 'de', 'German (Swiss)', @counter := @counter + 1),
(@option_group_id_languages, 0, 1, 'es_PR', 'es', 'Spanish; Castilian (Puerto Rico)', @counter := @counter + 1) [nativecode=1048 ** Column 'weight' cannot be null]
    [to_string] => [db_error: message="DB Error: constraint violation" code=-3 mode=callback callback=CRM_Core_Error::handle prefix="" info="INSERT INTO civicrm_option_value
  (option_group_id, is_default, is_active, name, value, label, weight)
VALUES
(@option_group_id_languages, 0, 1, 'de_CH', 'de', 'German (Swiss)', @counter := @counter + 1),
(@option_group_id_languages, 0, 1, 'es_PR', 'es', 'Spanish; Castilian (Puerto Rico)', @counter := @counter + 1) [nativecode=1048 ** Column 'weight' cannot be null]"]
)

Same issue or do you want me to file it separately?

[robinhood]

I have to say that I am disappointed that this issue has been known for almost a month and yet the 3.4.5 upgrade is still offered to civicrm users.   I am now reinstalling from backup which will cost me some unnecessary hours.  I wish someone had marked this version as having an issue with upgrades.

[Donald Lobo]

doing a point release takes a fair amount of time and effort. This basically also translates into actual hours Many of us on the core team were slammed with consulting / civicon / sprints / training / travel / vacation (make your own excuse here) and hence the delay.

We hope to get a release out in the next few weeks. You can help other folks avoid disappointment by getting more involved and helping with the releases. Some good ideas to help out are on this blog post: http://civicrm.org/blogs/davem/marketing-civicrm

lobo

[Slovak]

In the meantime, is there a feasible workaround to this upgrade issue?