Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0007792
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] 00. Application dictionarymajorhave not tried2009-02-24 11:032009-04-22 00:00
ReporteralostaleView Statuspublic 
Assigned Toalostale 
PrioritynormalResolutionfixedFixed in Version2.50
StatusclosedFix in branchFixed in SCM revision80c4691f81de
ProjectionnoneETAnoneTarget Versionpi
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionpiSCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0007792: 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.
TagsModularity
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
related to defect 0007623pi closedalostale Columnname check is not following the modularity rules 

-  Notes
(0014129)
alostale (manager)
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 (developer)
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
---

- Issue History
Date Modified Username Field Change
2009-02-24 11:03 alostale New Issue
2009-02-24 11:03 alostale Assigned To => alostale
2009-02-24 11:03 alostale Regression testing => No
2009-02-24 11:04 alostale Tag Attached: Modularity
2009-02-24 11:04 alostale Relationship added related to 0007623
2009-02-24 12:29 rafaroda version => trunk
2009-02-27 11:01 alostale Severity minor => major
2009-02-27 11:01 alostale Note Added: 0014129
2009-02-27 11:38 hgbot Checkin
2009-02-27 11:38 hgbot Note Added: 0014132
2009-02-27 11:38 hgbot Status new => resolved
2009-02-27 11:38 hgbot Resolution open => fixed
2009-02-27 11:38 hgbot Fixed in SCM revision => http://code.openbravo.com/erp/devel/pi/rev/80c4691f81de4076b97b132e57277251ad86139e [^]
2009-04-21 10:54 psarobe Status resolved => closed
2009-04-22 00:00 anonymous sf_bug_id 0 => 2778002


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker