Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0008510Openbravo ERPY. DBSourceManagerpublic2009-04-08 15:522009-06-18 00:00
Reporterplujan 
Assigned Tomarvintm 
PriorityurgentSeveritymajorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Versionmain 
Target VersionpiFixed in Version2.50MP1 
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
Summary0008510: The modified check constraints are taken as new ones for the upgrader
DescriptionUpgrading from 2.40mp3 to 2.50 I noted that if I have a modified "check constraint" to a AD table (i.e. in ad_window), it is identified as a new customization so the upgrade will add it to my custom code. The problem is that when exporting the model, upgrader tries to add my constraint and generates a conflict with current constraint.
Steps To ReproduceIn a 2.40, modify a check constraint. For example, you can do some innocuous change like "chr(?)" -> "chr(chr(?))"
Update to 2.50. Your module will have a modifiedTables folder with this change.
Run an export.database and you will get a "build failed" when trying to add multiple checks to the same.
Proposed Solution
Additional Information
Tags250MP1
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2009-04-08 15:52plujanNew Issue
2009-04-08 15:52plujanAssigned To => marvintm
2009-04-08 15:52plujanRegression testing => No
2009-04-22 18:47psarobePrioritynormal => urgent
2009-04-22 18:47psarobeStatusnew => scheduled
2009-04-23 16:04psarobeTag Attached: 250MP1
2009-04-28 16:54hgbotCheckin
2009-04-28 16:54hgbotNote Added: 0015866
2009-04-28 16:54hgbotStatusscheduled => resolved
2009-04-28 16:54hgbotResolutionopen => fixed
2009-04-28 16:54hgbotCheckin
2009-04-28 16:54hgbotNote Added: 0015867
2009-04-28 16:54hgbotFixed in SCM revision => http://code.openbravo.com/erp/devel/pi/rev/6a8cd9546838034c78c06c114bff337ea199589c [^]
2009-06-17 10:31plujanStatusresolved => closed
2009-06-18 00:00anonymoussf_bug_id0 => 2807990

Notes
(0015866)
hgbot   
2009-04-28 16:54   
Repository: dbsourcemanager
Revision: 295
Author: marvintm
Date: 2009-04-28 16:54:20 +0200 (Tue, 28 Apr 2009)

Fixed issue 8510. Now checks (and other table objects) shouldn't collide when the model is being merged (the newer ones will replace the older ones).

---
U trunk/src/org/apache/ddlutils/alteration/AddCheckChange.java
U trunk/src/org/apache/ddlutils/alteration/AddIndexChange.java
U trunk/src/org/apache/ddlutils/alteration/AddUniqueChange.java
U trunk/src/org/apache/ddlutils/alteration/AddViewChange.java
U trunk/src/org/apache/ddlutils/model/Database.java
U trunk/src/org/apache/ddlutils/model/Table.java
---

https://dev.openbravo.com/websvn/dbsourcemanager/?rev=295&sc=1 [^]
(0015867)
hgbot   
2009-04-28 16:54   
Repository: erp/devel/pi
Changeset: 6a8cd9546838034c78c06c114bff337ea199589c
Author: Antonio Moreno <antonio.moreno <at> openbravo.com>
Date: Tue Apr 28 16:54:32 2009 +0200
URL: http://code.openbravo.com/erp/devel/pi/rev/6a8cd9546838034c78c06c114bff337ea199589c [^]

Fixed issue 8510. Now checks (and other table objects) shouldn't collide when the model is being merged (the newer ones will replace the older ones).

---
M src-db/database/lib/dbsourcemanager.jar
---