Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
| ID | ||||||||
| 0015960 | ||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
| backport | [Openbravo ERP] Y. DBSourceManager | major | always | 2011-02-11 18:32 | 2011-02-22 20:20 | |||
| Reporter | egoitz | View Status | public | |||||
| Assigned To | marvintm | |||||||
| Priority | urgent | Resolution | fixed | Fixed in Version | ||||
| Status | closed | Fix in branch | 2.50 | Fixed in SCM revision | 2639703ba498 | |||
| Projection | none | ETA | none | Target Version | 2.50MP28 | |||
| OS | Any | Database | PostgreSQL | Java version | ||||
| OS Version | Database version | Ant version | ||||||
| Product Version | 2.50MP25 | SCM revision | ||||||
| Review Assigned To | ||||||||
| Web browser | ||||||||
| Modules | Core | |||||||
| Regression level | ||||||||
| Regression date | ||||||||
| Regression introduced in release | ||||||||
| Regression introduced by commit | ||||||||
| Triggers an Emergency Pack | No | |||||||
| Summary | 0015960: If you add an exeception for a trigger of a module different that core, this is not correctly managed | |||||||
| Description | If you add an exeception for a trigger of a module different that core, this is not correctly managed. The trigger is correctly exported to your module, but when executing update.database, the trigger is replaced with the trigger of the original module. | |||||||
| Steps To Reproduce | -Install APRM -Modify a trigger from this module -Add a new module, check it as indevelopment. -Add an exception for the trigger modified -Export the module. -See that the module is correctly exported to your module -Execute: update.database *see that the module on the database is the original from ARPM instead of the trigger exported as exception. | |||||||
| Tags | No tags attached. | |||||||
| Attached Files | ||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
||||||||
|
||||||||
 Relationships |
|
Notes |
|
|
(0034315) hgbot (developer) 2011-02-22 15:21 |
Repository: erp/stable/2.50 Changeset: 2639703ba498b25483a988413d2aac8cb48e2a0a Author: Antonio Moreno <antonio.moreno <at> openbravo.com> Date: Tue Feb 22 15:20:51 2011 +0100 URL: http://code.openbravo.com/erp/stable/2.50/rev/2639703ba498b25483a988413d2aac8cb48e2a0a [^] Fixed issue 15960. Now RemoveTriggerChanges will be exported to the configuration scripts. --- M src-db/database/lib/dbsourcemanager.jar --- |
|
(0034327) shuehner (administrator) 2011-02-22 20:20 |
Tested on pi/pgsql (rev: 811e1c898389) and stable/2.50/oracle (rev: 2938f20924f4). A removed triggers is added to the config.script on export, but a changed trigger (technically a removal/add is not). On a subsequent update.database that trigger is not re-created and if the trigger is really removed from its containing module the planned deletion declared in the config.script is a no-op. -> Closing |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2011-02-14 08:18 | alostale | Type | defect => backport |
| 2011-02-14 08:18 | alostale | fix_in_branch | => 2.50 |
| 2011-02-14 12:36 | marvintm | Target Version | 2.50MP27 => 2.50MP28 |
| 2011-02-22 15:21 | hgbot | Checkin | |
| 2011-02-22 15:21 | hgbot | Note Added: 0034315 | |
| 2011-02-22 15:21 | hgbot | Status | scheduled => resolved |
| 2011-02-22 15:21 | hgbot | Resolution | open => fixed |
| 2011-02-22 15:21 | hgbot | Fixed in SCM revision | => http://code.openbravo.com/erp/stable/2.50/rev/2639703ba498b25483a988413d2aac8cb48e2a0a [^] |
| 2011-02-22 20:20 | shuehner | Note Added: 0034327 | |
| 2011-02-22 20:20 | shuehner | Status | resolved => closed |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |