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

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0008031
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] A. Platformmajoralways2009-03-09 16:322009-04-22 00:01
ReportershuehnerView Statuspublic 
Assigned Tomtaal 
PrioritynormalResolutionfixedFixed in Version2.50
StatusclosedFix in branchFixed in SCM revision52cb0e69a9dc
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

0008031: export.database (for core) fails with new column of new module inside core table

DescriptionAdding a new column in a newly created module to a column in a core table and then doing export.database with having core and the new module indevelopment='Y' fails.

Error message is that the new column is present in the application dictionary but not in the database, even when it is in the db,
Steps To Reproduce- Create a new module (just entry in the application, no need to register it)
  - set the new module as indevelopment
  - set the dbprefix to: 'howto'
- set the core-module to indevelopment
- Add a new db-column to an existing core table:
ALTER TABLE m_productprice ADD COLUMN em_howto_calc_average_price CHARACTER(1) NOT NULL DEFAULT ;
- Go to Tables and columns and navigate to the m_productprice table. Use the 'create columns from database' to import the new column into the application distionary.
- Change the module for the new column to the newly created module.
- try to use 'ant export.database'

See the described error message when trying to export the core module.
TagsNo tags attached.
Attached Filesdiff file icon workaround_to_highlight_problem.diff [^] (900 bytes) 2009-03-09 16:33 [Show Content]

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
(0014528)
shuehner (administrator)
2009-03-09 16:35

Attached patch to pinpoint the place where most likely the problem pops up. The lines commented out by the patch force the validation to be run for the new module (belonging to module A) when trying to export the module core. => column from a not in module core (not in list of columns read from ddlutils) => error column from ad does not exist in db.
(0014540)
hgbot (developer)
2009-03-10 10:51

Repository: erp/devel/pi
Changeset: 52cb0e69a9dcb63e811b14b717986a89bca4b6f5
Author: Martin Taal <martin.taal <at> openbravo.com>
Date: Tue Mar 10 10:50:52 2009 +0100
URL: http://code.openbravo.com/erp/devel/pi/rev/52cb0e69a9dcb63e811b14b717986a89bca4b6f5 [^]

Fixes issue 8031: export.database (for core) fails with new column of new module inside core table

---
M src/org/openbravo/service/system/DatabaseValidator.java
---

- Issue History
Date Modified Username Field Change
2009-03-09 16:32 shuehner New Issue
2009-03-09 16:32 shuehner Assigned To => mtaal
2009-03-09 16:32 shuehner Regression testing => No
2009-03-09 16:33 shuehner File Added: workaround_to_highlight_problem.diff
2009-03-09 16:35 shuehner Note Added: 0014528
2009-03-10 10:51 hgbot Checkin
2009-03-10 10:51 hgbot Note Added: 0014540
2009-03-10 10:51 hgbot Status new => resolved
2009-03-10 10:51 hgbot Resolution open => fixed
2009-03-10 10:51 hgbot Fixed in SCM revision => http://code.openbravo.com/erp/devel/pi/rev/52cb0e69a9dcb63e811b14b717986a89bca4b6f5 [^]
2009-04-21 10:53 psarobe Status resolved => closed
2009-04-22 00:01 anonymous sf_bug_id 0 => 2778058


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker