Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
ID | ||||||||||||
0019071 | ||||||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
design defect | [Openbravo ERP] Y. DBSourceManager | major | have not tried | 2011-11-15 12:22 | 2012-09-24 21:01 | |||||||
Reporter | marvintm | View Status | public | |||||||||
Assigned To | marvintm | |||||||||||
Priority | normal | Resolution | open | Fixed in Version | ||||||||
Status | scheduled | Fix in branch | Fixed in SCM revision | |||||||||
Projection | none | ETA | none | Target Version | ||||||||
OS | Any | Database | Any | Java version | ||||||||
OS Version | Database version | Ant version | ||||||||||
Product Version | 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 | 0019071: Special case in Oracle update.database should be changed | |||||||||||
Description | Currently, when a change in a table is detected by update.database in Oracle, the following is done: - If the change is a column addition, the column is not mandatory, it goes to the end of the table, and there are no more changes for that table, an "ALTER TABLE ADD column" change is done. - Otherwise, the table is recreated. The first case has the following problem: if the table has triggers associated, the new column has a default, the triggers are executed, and they fail for some reason, the column is not added. | |||||||||||
Steps To Reproduce | Add a new non-mandatory column with a default value to the end of a table in the XML files. Verify that when update.database is done, the triggers related to that table are executed. | |||||||||||
Proposed Solution | This special case in Oracle will be removed, and the table will be recreated always. | |||||||||||
Tags | No tags attached. | |||||||||||
Attached Files | ||||||||||||
Relationships [ Relation Graph ] [ Dependency Graph ] | |
Notes | |
(0044704) marvintm (developer) 2012-01-30 16:11 |
This issue requires more thought, as the proposed change would have negative performance implications. A different approach would be to maintain current ModelComparator behavior, and instead move the Trigger deactivation to an earlier stage (so model change occurs with the triggers disabled). In any case, this issue will be changed to a design defect. |
(0052414) AugustoMauch (administrator) 2012-09-24 21:01 |
Effort: 5 Impact: low Plan: mid |
Issue History | |||
Date Modified | Username | Field | Change |
2011-11-15 12:22 | marvintm | New Issue | |
2011-11-15 12:22 | marvintm | Assigned To | => marvintm |
2011-11-15 12:22 | marvintm | Modules | => Core |
2012-01-30 16:11 | marvintm | Note Added: 0044704 | |
2012-01-30 16:11 | marvintm | Type | defect => design defect |
2012-09-24 21:01 | AugustoMauch | Note Added: 0052414 | |
2012-09-24 21:01 | AugustoMauch | Status | new => scheduled |
Copyright © 2000 - 2009 MantisBT Group |