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

View Issue Details[ Jump to Notes ] [ Issue History ] [ Print ]
ID
0021669
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] A. Platformmajoralways2012-09-17 12:172012-10-30 15:36
ReporterdmiguelezView Statuspublic 
Assigned ToAugustoMauch 
PrioritynormalResolutionfixedFixed in Version3.0MP17
StatusclosedFix in branchFixed in SCM revisionf412ba02b37b
ProjectionnoneETAnoneTarget Version
OSLinux 32 bitDatabasePostgreSQLJava version1.6.0_18
OS VersionCommunity ApplianceDatabase version8.3.9Ant version1.7.1
Product VersionSCM revision 
Merge Request Status
Review Assigned Tomarvintm
OBNetwork customerNo
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0021669: Validation when exporting Database not working properly.

DescriptionWhen Exporting the Database, there is a validation that checks that every column in the Database has a matching engtry in the Application Dictionary.
But it seems it is not working properly. There has been a regression already related to this Issue.
https://issues.openbravo.com/view.php?id=21614 [^]
Steps To ReproduceCreate a new column in the Database, for example in C_Invoice
Export it.
This column has no maching entry in the Application Dictionary and the validation has not warned about it.
TagsNo tags attached.
Attached Files? file icon issue21669.export [^] (3,090 bytes) 2012-10-11 17:57

- Relationships [ Relation Graph ] [ Dependency Graph ]

-  Notes
(0053322)
hgbot (developer)
2012-10-11 18:29

 Repository: erp/devel/pi
Changeset: f412ba02b37be45190c900ff5aa11b214732ebb8
Author: Augusto Mauch <augusto.mauch <at> openbravo.com>
Date: Thu Oct 11 13:51:24 2012 +0200
URL: http://code.openbravo.com/erp/devel/pi/rev/f412ba02b37be45190c900ff5aa11b214732ebb8 [^]

Fixes issue 21669: Validation when exporting Database not working properly

There was a validation that was only being done to the tables that belonged to the module being validated, but not to the tables modified by that module. Now, if a module adds a column to a table that belongs to another module but forgets to add it to the application dictionary, the validation will detect the error, the same way it has been working for the columns defined in tables that belonged to the module being validated.

---
M src/org/openbravo/service/system/DatabaseValidator.java
---
(0053336)
hudsonbot (viewer)
2012-10-13 15:50

 A changeset related to this issue has been promoted main and to the
Central Repository, after passing a series of tests.

Promotion changeset: https://code.openbravo.com/erp/devel/main/rev/99e438a6f972 [^]

Maturity status: Test

- Issue History
Date Modified Username Field Change
2012-09-17 12:17 dmiguelez New Issue
2012-09-17 12:17 dmiguelez Assigned To => AugustoMauch
2012-09-17 12:17 dmiguelez Modules => Core
2012-09-17 12:17 dmiguelez OBNetwork customer => No
2012-09-17 15:41 shuehner Issue Monitored: shuehner
2012-10-11 17:57 AugustoMauch File Added: issue21669.export
2012-10-11 18:28 AugustoMauch Issue Monitored: marvintm
2012-10-11 18:28 AugustoMauch Review Assigned To => marvintm
2012-10-11 18:29 hgbot Checkin
2012-10-11 18:29 hgbot Note Added: 0053322
2012-10-11 18:29 hgbot Status new => resolved
2012-10-11 18:29 hgbot Resolution open => fixed
2012-10-11 18:29 hgbot Fixed in SCM revision => http://code.openbravo.com/erp/devel/pi/rev/f412ba02b37be45190c900ff5aa11b214732ebb8 [^]
2012-10-13 15:50 hudsonbot Checkin
2012-10-13 15:50 hudsonbot Note Added: 0053336
2012-10-30 15:36 marvintm Status resolved => closed
2012-10-30 15:36 marvintm Fixed in Version => 3.0MP17

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker