Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0042089Openbravo ERPY. DBSourceManagerpublic2019-10-22 13:302019-11-28 16:02
ReporterAugustoMauch 
Assigned ToAugustoMauch 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version3.0PR20Q1 
Merge Request Status
Review Assigned Toalostale
OBNetwork customerNo
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0042089: Make ExportDatabase and CreateDatabase extensible so that they can be reused for the reporting project
DescriptionOne of the requisites of the Reporting Server project [1] is to be able to store in the Openbravo sources the model of the reporting database, and to be able to:
- Create the reporting model in the reporting database from these sources
- Export the reporting database model

The ExportDatabase and CreateDatabase classes are in charge of doing those tasks when both the Openbravo source data and the database model are stored in the same database.

It would be very useful to extend these classes so that they can export/import the model of a database other than the one that stores the source data.

[1] http://wiki.openbravo.com/wiki/Reporting_Server [^]
Steps To Reproduce-
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
related to feature request 00420423.0PR20Q1 closed AugustoMauch Add support of materialized views 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2019-10-22 13:30AugustoMauchNew Issue
2019-10-22 13:30AugustoMauchAssigned To => AugustoMauch
2019-10-22 13:30AugustoMauchOBNetwork customer => No
2019-10-22 13:30AugustoMauchModules => Core
2019-10-22 13:30AugustoMauchTriggers an Emergency Pack => No
2019-11-28 10:30AugustoMauchReview Assigned To => alostale
2019-11-28 10:30AugustoMauchStatusnew => scheduled
2019-11-28 10:33AugustoMauchNote Added: 0115926
2019-11-28 10:33AugustoMauchStatusscheduled => resolved
2019-11-28 10:33AugustoMauchFixed in Version => 3.0PR20Q1
2019-11-28 10:33AugustoMauchFixed in SCM revision => e7f2c0e1b428
2019-11-28 10:33AugustoMauchResolutionopen => fixed
2019-11-28 16:02alostaleStatusresolved => closed
2019-12-05 07:54alostaleRelationship addedrelated to 0042042

Notes
(0115926)
AugustoMauch   
2019-11-28 10:33   
The commit message was not proper, the issue was not updated accordingly.

These are the changesets that fixed this project:

DBSM

https://code.openbravo.com/erp/devel/dbsm-main/rev/e15403ffddfa [^]
https://code.openbravo.com/erp/devel/dbsm-main/rev/d1eaeb782297 [^]
https://code.openbravo.com/erp/devel/dbsm-main/rev/6c00b76c109c [^]
https://code.openbravo.com/erp/devel/dbsm-main/rev/3946ce75cb8c [^]
https://code.openbravo.com/erp/devel/dbsm-main/rev/afec5a40136e [^]
https://code.openbravo.com/erp/devel/dbsm-main/rev/31f9e4cdaec3 [^]

PI

https://code.openbravo.com/erp/devel/pi/rev/b67441bb6695 [^]
https://code.openbravo.com/erp/devel/pi/rev/46a3c417a130 [^]
https://code.openbravo.com/erp/devel/pi/rev/aa72afa35d67 [^]