Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0007580Openbravo ERP01. General setuppublic2009-02-16 17:052012-05-10 12:13
Reporterplujan 
Assigned Tomirurita 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusscheduledResolutionopen 
PlatformOS30OS Version
Product Versionpi 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0007580: If Organization Type contents change, an update.database will not update local copy
DescriptionIf I have an Openbravo release with old values on Organization Type window and a new revision update that content (by adding or updating rows) the update.database task will not update that table and old contents will remain.
Steps To Reproduce
Proposed SolutionIt has no sense to keep this records untouched. For other tables, like User, may be it is logic to keep records as user had them, but is not the same for Organization Type.
Additional Information
TagsOB3-Reviewed
Relationships
related to design defect 0008916 scheduled mirurita Organization window show a list of values in English when using Spanish 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2009-02-16 17:05plujanNew Issue
2009-02-16 17:05plujanAssigned To => rafaroda
2009-02-16 17:05plujanRegression testing => No
2009-02-18 04:30pjuvaraversion => trunk
2009-02-24 12:55psarobeStatusnew => scheduled
2009-02-24 12:55psarobeAssigned Torafaroda => marvintm
2009-02-24 12:55psarobefix_in_branch => trunk
2009-03-12 15:37marvintmNote Added: 0014611
2009-03-12 15:37marvintmAssigned Tomarvintm => vmromanos
2011-10-28 10:31psarobeTypedefect => design defect
2011-10-28 10:31psarobefix_in_branchpi =>
2011-10-28 10:31psarobeTag Attached: OB3-Reviewed
2011-11-24 15:30vmromanosRelationship addedrelated to 0008916
2012-05-10 12:13gorka_gilAssigned Tovmromanos => mirurita

Notes
(0014611)
marvintm   
2009-03-12 15:37   
This table currently belongs to dataset ADRD, and therefore will not be updated during the update.database process.

It should be decided whether this is correct or not. If it's not, then it should be moved to dataset AD. However, modularity will then need to be taken into account (an AD_MODULE_ID column will have to be added, or at least the whereclause will need to be modified to specify the module each row of this table belongs to).