Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0007414Openbravo ERP00. Application dictionarypublic2009-02-06 12:582009-02-20 09:54
Reportergforcada 
Assigned Toalostale 
PrioritylowSeveritytrivialReproducibilityalways
StatusclosedResolutionno change required 
PlatformOS5OS Version
Product Versionpi 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customerNo
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0007414: Auto-prefix AD elements (tables, columns ...) when selecting a "in development" data package
DescriptionIf 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.
Steps To Reproduce
Proposed Solution
Additional Information
TagsModularity
Relationships
related to defect 0007623pi closed alostale Columnname check is not following the modularity rules 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2009-02-06 12:58gforcadaNew Issue
2009-02-06 12:58gforcadaAssigned To => rafaroda
2009-02-06 12:58gforcadasf_bug_id0 => 2572252
2009-02-06 13:00rafarodaTag Attached: Modularity
2009-02-06 13:00gforcadaNote Added: 0013216
2009-02-09 09:36rafarodaOBNetwork customer => No
2009-02-09 09:36rafarodaversion => trunk
2009-02-17 11:28rafarodaAssigned Torafaroda => alostale
2009-02-17 11:28rafarodaPrioritynormal => low
2009-02-17 11:28rafarodaStatusnew => scheduled
2009-02-20 09:44alostaleRelationship addedrelated to 0007623
2009-02-20 09:54alostaleRegression testing => No
2009-02-20 09:54alostaleStatusscheduled => closed
2009-02-20 09:54alostaleNote Added: 0013804
2009-02-20 09:54alostaleResolutionopen => no change required

Notes
(0013216)
gforcada   
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   
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 [^]