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

View Issue Details[ Jump to Notes ] [ Issue History ] [ Print ]
ID
0007623
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] 00. Application dictionarymajoralways2009-02-18 13:222009-04-22 00:00
ReporteralostaleView Statuspublic 
Assigned Toalostale 
PriorityurgentResolutionfixedFixed in Version2.50beta
StatusclosedFix in branchFixed in SCM revision13310
ProjectionnoneETAnoneTarget Versionpi
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
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
Summary

0007623: Columnname check is not following the modularity rules

DescriptionModularity 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 Reproduce1. 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 SolutionCheck the columnanme in other for tables in different modules starts by EM_
TagsModularity
Attached Files

- Relationships [ Relation Graph ] [ Dependency Graph ]
has duplicate defect 0007680 closedalostale New Columns cannot be added with EM_XXX prefix 
has duplicate defect 0008630 closedalostale cannot switch module in tables and columns 
related to defect 0007414 closedalostale Auto-prefix AD elements (tables, columns ...) when selecting a "in development" data package 
related to defect 0007792pi closedalostale Not correct default module for column in a module different than their table's one. 

-  Notes
(0013647)
svnbot (viewer)
2009-02-18 13:23

 Repository: openbravo
Revision: 13310
Author: alostale
Date: 2009-02-18 13:23:23 +0100 (Wed, 18 Feb 2009)

fixed bug 0007623: Columnname check is not following the modularity rules

---
U trunk/src-db/database/model/triggers/AD_COLUMN_TRG2.xml
---

https://dev.openbravo.com/websvn/openbravo/?rev=13310&sc=1 [^]

- 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

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker