Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0004687Openbravo ERPY. DBSourceManagerpublic2008-08-22 18:152008-12-18 12:42
Reporternetworkb 
Assigned Tomarvintm 
PriorityimmediateSeveritycriticalReproducibilityalways
StatusclosedResolutionfixed 
PlatformOS20OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customerOBPS
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0004687: After update Openbravo to a version higher than 2.35mp5 the languages are deleted
DescriptionIf you update your application to a release higher that 2.35mp5 all the translations done are deleted.
Steps To Reproduce
Proposed Solution
Additional Information
Tagsdbsm_migrate
Relationships
related to defect 0005246 closed cromero If I have extra languages, updating process fails 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2008-08-22 18:15networkbNew Issue
2008-08-22 18:15networkbAssigned To => cromero
2008-08-22 18:15networkbsf_bug_id0 => 2067778
2008-08-22 18:15networkbOBNetwork customer => Yes
2008-08-22 18:15networkbRegression testing => No
2008-08-22 18:45psarobeProjectOpenbravo ERP => @4@
2008-08-25 12:31pjuvaraAssigned Tocromero => marvintm
2008-08-29 09:42pjuvaraPriorityhigh => immediate
2008-08-29 09:42pjuvaraSeveritymajor => critical
2008-08-29 09:42pjuvaraStatusnew => acknowledged
2008-08-29 09:42pjuvaraversion2.35MP7 =>
2008-09-16 09:05marvintmStatusacknowledged => scheduled
2008-09-16 09:05marvintmfix_in_branch => trunk
2008-09-16 09:08marvintmStatusscheduled => resolved
2008-09-16 09:08marvintmResolutionopen => fixed
2008-09-16 09:08marvintmNote Added: 0009025
2008-09-24 18:42cromeroRelationship addedrelated to 0005246
2008-11-25 23:02psarobeStatusresolved => closed
2008-12-18 12:38jpabloaeSticky IssueNo => Yes
2008-12-18 12:39jpabloaeSticky IssueYes => No
2008-12-18 12:39jpabloaeTag Attached: dbsm_migrate
2008-12-18 12:41jpabloaeProject@4@ => Openbravo ERP
2008-12-18 12:42jpabloaeCategoryF. Localization => Y. DBSourceManager

Notes
(0009025)
marvintm   
2008-09-16 09:08   
This should have never happened in the first place (the cause of this was a modification in the filters done after exporting the database, something that should never be done).

Now the update mechanism will not, in any case, delete the translations, except in the case that a translation doesn't correspond to an entry in the database (i.e., the entry has been deleted in the new version).

Still, foreign keys have to be changed to "ON DELETE CASCADE" in the Openbravo ERP for this mechanism to work. If they are not changed, the update might fail, as constraints could not be activated. However, even in that case, the translations wouldn't be deleted.