Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0011788Openbravo ERPY. DBSourceManagerpublic2009-12-15 13:192010-07-14 00:00
nataliaperu 
marvintm 
urgentmajoralways
closedfixed 
5
2.50MP9 
 
Core
No
0011788: Triggers are not exported when are added as naming exceptions
If a trigger is added as a naming exception, and export.database is executed, it is not exported into src-db folder.
Create a new module into AD. Set it as "In development".
Add a Naming exception. Use a Trigger, IE c_validcombination_trg.
Save it.
Execute ant export.database
No tags attached.
Issue History
2009-12-15 13:19nataliaperuNew Issue
2009-12-15 13:19nataliaperuAssigned To => marvintm
2010-01-04 13:05iciordiaPrioritynormal => urgent
2010-01-04 13:05iciordiaStatusnew => scheduled
2010-07-01 12:46hgbotCheckin
2010-07-01 12:46hgbotNote Added: 0028944
2010-07-01 12:46hgbotStatusscheduled => resolved
2010-07-01 12:46hgbotResolutionopen => fixed
2010-07-01 12:46hgbotFixed in SCM revision => http://code.openbravo.com/erp/devel/dbsm-main/rev/6109cf53d95653af56babb55362feb1aebf8bf11 [^]
2010-07-01 12:47hgbotCheckin
2010-07-01 12:47hgbotNote Added: 0028945
2010-07-01 12:47hgbotFixed in SCM revisionhttp://code.openbravo.com/erp/devel/dbsm-main/rev/6109cf53d95653af56babb55362feb1aebf8bf11 [^] => http://code.openbravo.com/erp/devel/pi/rev/2fb2af126d29de13301baffe4af0991aa43a6856 [^]
2010-07-02 14:51hudsonbotCheckin
2010-07-02 14:51hudsonbotNote Added: 0029002
2010-07-13 18:05iperdomoNote Added: 0029269
2010-07-13 18:05iperdomoStatusresolved => closed
2010-07-14 00:00anonymoussf_bug_id0 => 3029171

Notes
(0028944)
hgbot   
2010-07-01 12:46   
Repository: erp/devel/dbsm-main
Changeset: 6109cf53d95653af56babb55362feb1aebf8bf11
Author: Antonio Moreno <antonio.moreno <at> openbravo.com>
Date: Thu Jul 01 12:46:08 2010 +0200
URL: http://code.openbravo.com/erp/devel/dbsm-main/rev/6109cf53d95653af56babb55362feb1aebf8bf11 [^]

Fixed issue 11788. Fixed trigger exporting with naming exception
Now, if a trigger was added to a module via a naming exception, it will be exported in that module even if the ad_exception was added through the application. Before it worked like this, but only if the ad_exception had been created by the 2.40-2.50 upgrade utility (and thus, had the name2 column empty).

---
M src/org/apache/ddlutils/platform/ExcludeFilter.java
---
(0028945)
hgbot   
2010-07-01 12:47   
Repository: erp/devel/pi
Changeset: 2fb2af126d29de13301baffe4af0991aa43a6856
Author: Antonio Moreno <antonio.moreno <at> openbravo.com>
Date: Thu Jul 01 12:46:26 2010 +0200
URL: http://code.openbravo.com/erp/devel/pi/rev/2fb2af126d29de13301baffe4af0991aa43a6856 [^]

Fixed issue 11788. Fixed trigger exporting with naming exception
> Now, if a trigger was added to a module via a naming exception, it will be exported in that module even if the ad_exception was added through the application. Before it worked like this, but only if the ad_exception had been created by the 2.40-2.50 upgrade utility (and thus, had the name2 column empty).

---
M src-db/database/lib/dbsourcemanager.jar
---
(0029002)
hudsonbot   
2010-07-02 14:51   
A changeset related to this issue has been promoted to main after passing a series of tests and an OBX has been generated:

Changeset: http://code.openbravo.com/erp/devel/main/rev/2fb2af126d29 [^]
Merge Changeset: http://code.openbravo.com/erp/devel/main/rev/8fd5a427789e [^]
Tests: http://builds.openbravo.com/view/int/ [^]
OBX: http://builds.openbravo.com/erp/core/obx/OpenbravoERP-2.50CI.17797.obx [^]
(0029269)
iperdomo   
2010-07-13 18:05   
Tested on pi @ rev e12428e2fe3c