Anonymous | Login
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] A. Platformmajorhave not tried2020-03-19 21:072020-04-16 11:26
ReportermtaalView Statuspublic 
Assigned Toalostale 
PrioritynormalResolutionfixedFixed in VersionPR20Q3
StatusclosedFix in branchFixed in SCM revision5e3802cd030a
ProjectionnoneETAnoneTarget Versionpi
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned Tocaristu
Web browser
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo

0043527: Dbsourcemanager MaterializedView support: if MV depends on other MV order of execution can be wrong

DescriptionI have a MV which definition has a select statement on another MV (see [1]). Postgresql requires that the referenced MV already exists and will throw an error [2].

 SELECT r_1.obrtmd_org_id,
            sum(r_1.ticket_cnt) AS ticket_cnt,
            sum(r_1.line_gross_amount) AS line_gross_amount,
            sum(r_1.qtyordered) AS qty
           FROM obrts_order_stats_pr_dt_mv r_1

[createreportingdatabase] 4965 [main] WARN org.apache.ddlutils.platform.PGStandardBatchEvaluator - SQL Command failed with: ERROR: relation "obrts_order_stats_pr_dt_mv" does not exist
[createreportingdatabase] Position: 1194
Steps To ReproduceCreate a MV which depends another MV and then dbsourcemanager
Proposed SolutionUse module dependencies to find the order of MV creation. This is however not always sufficient. Other idea (given by AL) to ignore exceptions and just repeat failed MV creation in a loop until all MV are created or no remaining MV succeeds.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
alostale (developer)
2020-03-30 08:38

MR: [^]
hgbot (developer)
2020-04-09 10:25

Repository: erp/devel/pi
Changeset: 5e3802cd030a0a27b3d2bfb6c050bcc8bf375bea
Author: Asier Lostalé <asier.lostale <at>>
Date: Thu Apr 09 10:24:45 2020 +0200
URL: [^]

fixed BUG-43527: creation of materialized view depedending on another MV fails

Creation of materialized views depending on another materialized view
failed in case the dependency was not previously created.

Treating materialized views in the same way regular views are treated
adding FORCE = TRUE option so that it retries failed executions.

M src-db/database/lib/dbsourcemanager.jar
caristu (developer)
2020-04-16 11:26

Reviewed + tested OK

- Issue History
Date Modified Username Field Change
2020-03-19 21:07 mtaal New Issue
2020-03-19 21:07 mtaal Assigned To => alostale
2020-03-19 21:07 mtaal Modules => Core
2020-03-19 21:07 mtaal Triggers an Emergency Pack => No
2020-03-19 21:07 mtaal Issue Monitored: mtaal
2020-03-30 08:38 alostale Note Added: 0118861
2020-04-09 10:25 hgbot Checkin
2020-04-09 10:25 hgbot Note Added: 0119112
2020-04-09 10:25 hgbot Status new => resolved
2020-04-09 10:25 hgbot Resolution open => fixed
2020-04-09 10:25 hgbot Fixed in SCM revision => [^]
2020-04-10 10:12 alostale Review Assigned To => caristu
2020-04-16 11:26 caristu Note Added: 0119214
2020-04-16 11:26 caristu Status resolved => closed
2020-04-16 11:26 caristu Fixed in Version => 3.0PR20Q3

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker