Answers.Body: <p>It's not really an answer, but I did fiddle around with things enough to break it into working again.  I ended up dumping the DB to a backup, dropping both new columns, civicrm_price_field_value.help_pre_en_US and civicrm_price_field_value.help_post_en_US, then changing the DB version back to 4.7.9.  I then re-ran the upgrade and got a "Table already exists" error on another table.  Dumped the backup back into the DB, recreated the two columns from above, changed the version back, and now everything seems kosher for the most part.  I can add/delete/change price sets and therefore work with Events. Can't edit the broken events, but that's a leftover issue I can work around.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-08-25T19:14:25.157Z
Answers.LastActivityDate: 2016-08-25T19:14:25.157Z
Answers.UserDisplayName: G H
Answers.Body: <p>I believe it could be a trigger problem. The way the multilingual works in CiviCRM is that CiviCRM will only work on a language at a time using a sql view (e.g civicrm_price_field_value_en_US). When you create a new entity, a trigger ensure that every language is properly initialized by copying the multilingual column data to others languages. If the trigger is not up-to-date, it will fail to do this and can lead to the error you got.</p>
  
  <p>A way to solve that is to rebuild triggers like so : <a href="https://yoursite.org/civicrm/menu/rebuild?reset=1&amp;triggerRebuild=1" rel="nofollow noreferrer">https://yoursite.org/civicrm/menu/rebuild?reset=1&amp;triggerRebuild=1</a></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-12-16T19:07:37.553Z
Answers.Text: It's been a while, but if I remember correctly, the trigger rebuild died because of this problem.  I believe that the problem was permanently fixed in 4.7.13 after some cleanup based on this issue.  I believe it was https://issues.civicrm.org/jira/browse/CRM-19393.
Answers.UserDisplayName: G H
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-12-16T15:09:52.317Z
Answers.LastActivityDate: 2016-12-16T15:09:52.317Z
Answers.UserDisplayName: samuelsov
Body: <p>After upgrading to 4.7.10 from 4.7.9, I'm no longer able to edit/add price sets.  I think that the DB changes related to <a href="https://issues.civicrm.org/jira/browse/CRM-12252" rel="nofollow">https://issues.civicrm.org/jira/browse/CRM-12252</a> are biting me.  (Multi-lingual is enabled.)  I don't recall any problems with the upgrade.  However, now the DB error says:
      [debug_info] => UPDATE civicrm_price_field_value_en_US SET is_default = 0 WHERE  price_field_id = 27 [nativecode=1054 ** Unknown column 'help_pre_en_US' in 'field list']</p>
  
  <p>I can reproduce this same error by editing any field for any record in the civicrm_price_field_value table and the civicrm_price_field_value_en_US view via phpMyAdmin.  The field does exist,  I've recreated the View, and dropped the column and recreated it. Other _en_US tables are unaffected.  (Yes, I've cleared CiviCRM caches, and run commands in Private windows to try to get away from cache poisoning.)</p>
  
  <p>This is happening after the upgrade, with new data since the pre-upgrade backup on a live server.  Rolling back isn't really an option.  There must be something that needs to be refreshed, but I can't find it.  Any ideas?</p>
  
  <p>Wordpress 4.6
  CiviCRM 4.7.10</p>
  
  <p>Another bit of weirdness that points toward a failed DB upgrade:  The COMMENT portion of the two new fields is not there, but both fields are decidedly there.</p>
  
Tags: <wordpress><upgrade><database><i18n>
Title: DB table that exists says it doesn't
ThreadText: # DB table that exists says it doesn't
  
  (Asked by: username_0 on 2016-08-24)
  
  After upgrading to 4.7.10 from 4.7.9, I'm no longer able to edit/add price sets. I think that the DB changes related to <https://issues.civicrm.org/jira/browse/CRM-12252> are biting me. (Multi-lingual is enabled.) I don't recall any problems with the upgrade. However, now the DB error says:
  [debug\_info] => UPDATE civicrm\_price\_field\_value\_en\_US SET is\_default = 0 WHERE price\_field\_id = 27 [nativecode=1054 \*\* Unknown column 'help\_pre\_en\_US' in 'field list']
  
  I can reproduce this same error by editing any field for any record in the civicrm\_price\_field\_value table and the civicrm\_price\_field\_value\_en\_US view via phpMyAdmin. The field does exist, I've recreated the View, and dropped the column and recreated it. Other \_en\_US tables are unaffected. (Yes, I've cleared CiviCRM caches, and run commands in Private windows to try to get away from cache poisoning.)
  
  This is happening after the upgrade, with new data since the pre-upgrade backup on a live server. Rolling back isn't really an option. There must be something that needs to be refreshed, but I can't find it. Any ideas?
  
  Wordpress 4.6
  CiviCRM 4.7.10
  
  Another bit of weirdness that points toward a failed DB upgrade: The COMMENT portion of the two new fields is not there, but both fields are decidedly there.
  
  **Tags:** wordpress, upgrade, database, i18n
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_0 on 2016-08-25. Score: 1 | Accepted answer
  
  It's not really an answer, but I did fiddle around with things enough to break it into working again. I ended up dumping the DB to a backup, dropping both new columns, civicrm\_price\_field\_value.help\_pre\_en\_US and civicrm\_price\_field\_value.help\_post\_en\_US, then changing the DB version back to 4.7.9. I then re-ran the upgrade and got a "Table already exists" error on another table. Dumped the backup back into the DB, recreated the two columns from above, changed the version back, and now everything seems kosher for the most part. I can add/delete/change price sets and therefore work with Events. Can't edit the broken events, but that's a leftover issue I can work around.
  
  
  ---
  
  ### Answer by username_1 on 2016-12-16. Score: 0
  
  I believe it could be a trigger problem. The way the multilingual works in CiviCRM is that CiviCRM will only work on a language at a time using a sql view (e.g civicrm\_price\_field\_value\_en\_US). When you create a new entity, a trigger ensure that every language is properly initialized by copying the multilingual column data to others languages. If the trigger is not up-to-date, it will fail to do this and can lead to the error you got.
  
  A way to solve that is to rebuild triggers like so : <https://yoursite.org/civicrm/menu/rebuild?reset=1&triggerRebuild=1>
  
  > **Comments:**
  > **username_0**: It's been a while, but if I remember correctly, the trigger rebuild died because of this problem.  I believe that the problem was permanently fixed in 4.7.13 after some cleanup based on this issue.  I believe it was https://issues.civicrm.org/jira/browse/CRM-19393.  
  
  ---
  
  