Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0007792Openbravo ERP00. Application dictionarypublic2009-02-24 11:032009-04-22 00:00
Reporteralostale 
Assigned Toalostale 
PrioritynormalSeveritymajorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Versionpi 
Target VersionpiFixed in Version2.50 
Merge Request Status
Review Assigned To
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0007792: Not correct default module for column in a module different than their table's one.
DescriptionWhen a column is created within another module than its table's one the process that creates the column from DB inserts it in the table's module instead in the one it should be in according to the naming rules.
Steps To Reproduce-Create a new module with DB prefix (example TEST).
-Create a new column in DB for a core table. This column must be added to the test module according to naming rules. For example C_INVOICE.EM_TEST_MYCOLUMN.
-Set test and core modules as in development.
-Go to Application Dictionary || Tables and Columns || Table.
-Select C_Invoice table
-Click Create Column From DB. Check a new column has been created.
-Go to the column tab and select the new one. Check that its module is not test but core.
Proposed SolutionTake into account naming rules when creating new columns in application dictionary.
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-24 11:03alostaleNew Issue
2009-02-24 11:03alostaleAssigned To => alostale
2009-02-24 11:03alostaleRegression testing => No
2009-02-24 11:04alostaleTag Attached: Modularity
2009-02-24 11:04alostaleRelationship addedrelated to 0007623
2009-02-24 12:29rafarodaversion => trunk
2009-02-27 11:01alostaleSeverityminor => major
2009-02-27 11:01alostaleNote Added: 0014129
2009-02-27 11:38hgbotCheckin
2009-02-27 11:38hgbotNote Added: 0014132
2009-02-27 11:38hgbotStatusnew => resolved
2009-02-27 11:38hgbotResolutionopen => fixed
2009-02-27 11:38hgbotFixed in SCM revision => http://code.openbravo.com/erp/devel/pi/rev/80c4691f81de4076b97b132e57277251ad86139e [^]
2009-04-21 10:54psarobeStatusresolved => closed
2009-04-22 00:00anonymoussf_bug_id0 => 2778002

Notes
(0014129)
alostale   
2009-02-27 11:01   
Changed severity to major.

Note that another big issue with this is that as it is trying to insert the new column in core, in case core is not in development it will raise an error because it is not possible to insert new elements in a module not in development. Forcing to have core in development, which does not make sense when developing new modules.
(0014132)
hgbot   
2009-02-27 11:38   
Repository: erp/devel/pi
Changeset: 80c4691f81de4076b97b132e57277251ad86139e
Author: Asier Lostalé <asier.lostale <at> openbravo.com>
Date: Fri Feb 27 11:37:44 2009 +0100
URL: http://code.openbravo.com/erp/devel/pi/rev/80c4691f81de4076b97b132e57277251ad86139e [^]

fixed bug 0007792: Not correct default module for column in a module different than their table's one.

---
M src-db/database/model/functions/AD_TABLE_IMPORT.xml
---