Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
| ID | ||||||||
| 0007414 | ||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
| defect | [Openbravo ERP] 00. Application dictionary | trivial | always | 2009-02-06 12:58 | 2009-02-20 09:54 | |||
| Reporter | gforcada | View Status | public | |||||
| Assigned To | alostale | |||||||
| Priority | low | Resolution | no change required | Fixed in Version | ||||
| Status | closed | 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 | pi | 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 | 0007414: Auto-prefix AD elements (tables, columns ...) when selecting a "in development" data package | |||||||
| Description | If you are in Application Dictionary || Tables and Columns || Table and are developing a module, Openbravo ERP shouldn't complain that the "Name" and "DB Table Name" aren't started with the module's DB prefix. Instead, it should either auto-fill the prefixes in the corresponding fields when the user selects a Data package or when saving the record warn the user and asks if Openbravo ERP should prefix the current fields that aren't already prefixed. | |||||||
| Tags | Modularity | |||||||
| Attached Files | ||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
||||||||
|
||||||||
 Relationships |
|
Notes |
|
|
(0013216) gforcada (reporter) 2009-02-06 13:00 |
I filed as a defect since applications are meant to be useful to users not a complaining system to annoy the user that tries to use it. Feel free to change as a feature request. |
|
(0013804) alostale (manager) 2009-02-20 09:54 |
This is the correct behavior according with the modularity specifications (naming rules) [1] and [2]. Note that it is not only application dictionary but also physical database, this is done in this way to prevent naming clashes between different modules. [1] http://wiki.openbravo.com/wiki/Projects/Modularity/Specifications#Naming_and_packaging_rules [^] [2] http://wiki.openbravo.com/wiki/Projects/Modularity/Developers_Guide#Table_and_column [^] |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2009-02-06 12:58 | gforcada | New Issue | |
| 2009-02-06 12:58 | gforcada | Assigned To | => rafaroda |
| 2009-02-06 12:58 | gforcada | sf_bug_id | 0 => 2572252 |
| 2009-02-06 13:00 | rafaroda | Tag Attached: Modularity | |
| 2009-02-06 13:00 | gforcada | Note Added: 0013216 | |
| 2009-02-09 09:36 | rafaroda | version | => trunk |
| 2009-02-17 11:28 | rafaroda | Assigned To | rafaroda => alostale |
| 2009-02-17 11:28 | rafaroda | Priority | normal => low |
| 2009-02-17 11:28 | rafaroda | Status | new => scheduled |
| 2009-02-20 09:44 | alostale | Relationship added | related to 0007623 |
| 2009-02-20 09:54 | alostale | Regression testing | => No |
| 2009-02-20 09:54 | alostale | Status | scheduled => closed |
| 2009-02-20 09:54 | alostale | Note Added: 0013804 | |
| 2009-02-20 09:54 | alostale | Resolution | open => no change required |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |