Openbravo Issue Tracking System - Openbravo ERP |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0007623 | Openbravo ERP | 00. Application dictionary | public | 2009-02-18 13:22 | 2009-04-22 00:00 |
|
| Reporter | alostale | |
| Assigned To | alostale | |
| Priority | urgent | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | |
| Platform | | OS | 5 | OS Version | |
| Product Version | | |
| Target Version | pi | Fixed in Version | 2.50beta | |
| Merge Request Status | |
| Review Assigned To | |
| OBNetwork customer | No |
| Web browser | |
| Modules | Core |
| Support ticket | |
| Regression level | |
| Regression date | |
| Regression introduced in release | |
| Regression introduced by commit | |
| Triggers an Emergency Pack | No |
|
| Summary | 0007623: Columnname check is not following the modularity rules |
| Description | Modularity defines that a column in a module can be added to a table in a different module, in this case the column name should be EM_DBPREFIX_COLUMNNAME.
But the trigger that checks the name correctness for the columns fails when following this policy because it does not check it starts by EM_. |
| Steps To Reproduce | 1. Create a new module and set a dbprefix, let's say TEST.
2. Create a new DB column in a core table called EM_TEST_MYCOLUMN
3. Add this column to dictionary and set it to the new module. -> An error is raised. |
| Proposed Solution | Check the columnanme in other for tables in different modules starts by EM_ |
| Additional Information | |
| Tags | Modularity |
| Relationships | | has duplicate | defect | 0007680 | | closed | alostale | New Columns cannot be added with EM_XXX prefix | | has duplicate | defect | 0008630 | | closed | alostale | cannot switch module in tables and columns | | related to | defect | 0007414 | | closed | alostale | Auto-prefix AD elements (tables, columns ...) when selecting a "in development" data package | | related to | defect | 0007792 | pi | closed | alostale | Not correct default module for column in a module different than their table's one. |
|
| Attached Files | |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2009-02-18 13:22 | alostale | New Issue | |
| 2009-02-18 13:22 | alostale | Assigned To | => alostale |
| 2009-02-18 13:22 | alostale | OBNetwork customer | => No |
| 2009-02-18 13:22 | alostale | Regression testing | => No |
| 2009-02-18 13:22 | alostale | Tag Attached: Modularity | |
| 2009-02-18 13:23 | svnbot | Checkin | |
| 2009-02-18 13:23 | svnbot | Note Added: 0013647 | |
| 2009-02-18 13:23 | svnbot | Status | new => resolved |
| 2009-02-18 13:23 | svnbot | Resolution | open => fixed |
| 2009-02-18 13:23 | svnbot | svn_revision | => 13310 |
| 2009-02-20 09:44 | alostale | Relationship added | related to 0007414 |
| 2009-02-24 11:04 | alostale | Relationship added | related to 0007792 |
| 2009-02-24 12:00 | alostale | Relationship added | has duplicate 0007680 |
| 2009-04-21 10:33 | psarobe | Status | resolved => closed |
| 2009-04-22 00:00 | anonymous | sf_bug_id | 0 => 2777951 |
| 2009-04-23 12:25 | alostale | Relationship added | has duplicate 0008630 |