Openbravo Issue Tracking System - Openbravo ERP |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0014329 | Openbravo ERP | K. Packaging | public | 2010-08-26 18:17 | 2010-08-26 18:22 |
|
| Reporter | Xpand-IT | |
| Assigned To | marvintm | |
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | new | Resolution | open | |
| Platform | | OS | 5 | OS Version | |
| Product Version | | |
| Target Version | | Fixed in Version | | |
| Merge Request Status | |
| Review Assigned To | |
| OBNetwork customer | |
| Web browser | |
| Modules | Core |
| Support ticket | |
| Regression level | |
| Regression date | |
| Regression introduced in release | |
| Regression introduced by commit | |
| Triggers an Emergency Pack | No |
|
| Summary | 0014329: On export.database when a trigger name starts with EM_ show a warning that this is incorrect and will be ignored |
| Description | Triggers should never be named as EM_Dbprefix_TrigerName. However, it's quite easy for someone to make this mistake as using EM_ is part of columns naming conventions. |
| Steps To Reproduce | |
| Proposed Solution | If there is a trigger starting with EM_, it would be helpful to get a warning saying that it is wrong and it's going to be ignored. |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | |
| Attached Files | |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2010-08-26 18:17 | Xpand-IT | New Issue | |
| 2010-08-26 18:17 | Xpand-IT | Assigned To | => jpabloae |
| 2010-08-26 18:17 | Xpand-IT | Issue Monitored: Xpand-IT | |
| 2010-08-26 18:22 | jpabloae | Assigned To | jpabloae => marvintm |