Openbravo Issue Tracking System - Openbravo ERP  | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update | 
| 0014583 | Openbravo ERP | 00. Application dictionary | public | 2010-09-16 12:21 | 2022-02-01 08:08 | 
| Reporter | albertobg | ||||
| Assigned To | Triage Platform Base | ||||
| Priority | normal | Severity | major | Reproducibility | have not tried | 
| Status | acknowledged | Resolution | open | ||
| Platform | OS | 5 | OS Version | ||
| Product Version | 2.50MP20 | ||||
| Target Version | Fixed in Version | ||||
| Merge Request Status | |||||
| Review Assigned To | |||||
| OBNetwork customer | No | ||||
| Web browser | |||||
| Modules | Core | ||||
| Support ticket | |||||
| Regression level | |||||
| Regression date | |||||
| Regression introduced in release | |||||
| Regression introduced by commit | |||||
| Triggers an Emergency Pack | No | ||||
| Summary | 0014583: Uninstall and install a module fails in some circumstances | ||||
| Description | We have a module "A" that has a tab with name "Tab A", installed in a machine. Then we create a module "B" that have too a tab with name "Tab A". If we uninstall the module "A" and install the module "B", when update database is done, it fails because a constraint of unique name of tab. We find in the database that exists a record in AD_TAB of a module that not exists in AD_MODULE (the module "A" that was uninstalled) and a record in AD_TABLE of the same module. So, the uninstallation of module "A" is not complete when module "B" has a tab with the same name. We delete manually the record in AD_TAB and AD_TABLE and update database is done.  | ||||
| Steps To Reproduce | -Create module A with a tab name "Tab test" -Install it on a machine -Create module B with a tab name "Tab test" -Uninstall module A and install module B -Apply changes. Then the update.database fails.  | ||||
| Proposed Solution | |||||
| Additional Information | |||||
| Tags | OB3-Reviewed | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2010-09-16 12:21 | albertobg | New Issue | |||
| 2010-09-16 12:21 | albertobg | Assigned To | => alostale | ||
| 2010-09-16 12:47 | albertobg | Note Added: 0031153 | |||
| 2010-09-17 09:37 | adrianromero | OBNetwork customer | => No | ||
| 2010-09-20 09:02 | alostale | Priority | high => urgent | ||
| 2010-09-20 09:02 | alostale | Severity | critical => major | ||
| 2010-09-20 09:03 | alostale | Status | new => scheduled | ||
| 2010-09-20 09:03 | alostale | fix_in_branch | => pi | ||
| 2011-10-29 22:03 | psarobe | Tag Attached: OB3-Reviewed | |||
| 2012-05-08 17:35 | alostale | Type | defect => design defect | ||
| 2012-05-08 17:35 | alostale | fix_in_branch | pi => | ||
| 2012-09-24 23:30 | AugustoMauch | Note Added: 0052482 | |||
| 2012-09-24 23:30 | AugustoMauch | Priority | urgent => normal | ||
| 2017-03-31 14:36 | alostale | Status | scheduled => acknowledged | ||
| 2017-04-10 14:34 | alostale | Assigned To | alostale => platform | ||
| 2022-02-01 08:08 | alostale | Assigned To | platform => Triage Platform Base | ||
| Notes | |||||
| 
		 | 
|||||
		
  | 
	
		
  | 
||||
| 
		 | 
|||||
		
  | 
	
		
  | 
||||