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

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0008478
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] A. Platformmajorhave not tried2009-04-07 09:552009-06-04 00:00
ReportermarvintmView Statuspublic 
Assigned Toalostale 
PrioritynormalResolutionfixedFixed in Version2.50MP1
StatusclosedFix in branchFixed in SCM revisionbcb4997e10a9
ProjectionnoneETAnoneTarget Version
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

0008478: AD_Column trigger should take into account the AD_Exceptions table when checking for naming rules compliance

DescriptionTrigger AD_Column_trg2 checks if column names comply with modularity naming rules when a row in table AD_Column is added or modified. The problem is that it doesn't take into account the AD_Exceptions table.

This means that when a database has been updated from an earlier version of Openbravo, you will get an error message every time you try to modify a column, because customized columns don't comply with naming rules, and although the upgrade process adds them to the ad_exceptions table, the trigger doesn't check that.
Proposed SolutionModify the trigger so that it takes into account not only the naming of the column but also if it has been added as a naming exception or not.
TagsModularity
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
(0015917)
hgbot (developer)
2009-04-29 13:14

Repository: erp/devel/pi
Changeset: bcb4997e10a9e7b19e34eb7958781c5fdc43d46f
Author: Asier Lostalé <asier.lostale <at> openbravo.com>
Date: Wed Apr 29 13:14:03 2009 +0200
URL: http://code.openbravo.com/erp/devel/pi/rev/bcb4997e10a9e7b19e34eb7958781c5fdc43d46f [^]

fixed bug 0008478: AD_Column trigger should take into account the AD_Exceptions table when checking for naming rules compliance

---
M src-db/database/model/triggers/AD_COLUMN_TRG2.xml
---

- Issue History
Date Modified Username Field Change
2009-04-07 09:55 marvintm New Issue
2009-04-07 09:55 marvintm Assigned To => rafaroda
2009-04-07 09:55 marvintm Regression testing => No
2009-04-22 17:33 psarobe Assigned To rafaroda => alostale
2009-04-22 17:33 psarobe Status new => scheduled
2009-04-23 12:28 alostale Tag Attached: Modularity
2009-04-24 16:53 rafaroda version => pi
2009-04-29 13:14 hgbot Checkin
2009-04-29 13:14 hgbot Note Added: 0015917
2009-04-29 13:14 hgbot Status scheduled => resolved
2009-04-29 13:14 hgbot Resolution open => fixed
2009-04-29 13:14 hgbot Fixed in SCM revision => http://code.openbravo.com/erp/devel/pi/rev/bcb4997e10a9e7b19e34eb7958781c5fdc43d46f [^]
2009-06-03 17:47 psarobe Status resolved => closed
2009-06-04 00:00 anonymous sf_bug_id 0 => 2800768


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker