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

View Issue Details[ Jump to Notes ] [ Issue History ] [ Print ]
ID
0039520
TypeCategorySeverityReproducibilityDate SubmittedLast Update
backport[Openbravo ERP] A. Platformminorhave not tried2018-10-23 16:302018-10-29 11:22
ReporteralostaleView Statuspublic 
Assigned Toalostale 
PrioritynormalResolutionfixedFixed in Version3.0PR18Q4
StatusclosedFix in branchFixed in SCM revision10877055b912
ProjectionnoneETAnoneTarget Version3.0PR18Q4
OSAnyDatabasePostgreSQLJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Merge Request Status
Review Assigned Tocaristu
OBNetwork customerNo
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0039520: PG 10: false local changes positive after restoring PG 9.3 dump

DescriptionHaving a PostgreSQL 10 or 11 database created from a dump obtained from 9.3, updata.database incorrectly detects local changes in DB structure.

Workarround: execute 1st update with -Dforce=true parameter.
Steps To Reproduce1. Install Openbravo (at least 18Q1) in PostgreSQL 9.3 (ie. Openbravo Appliance 14.04)
2. Do a pg_dump
3. Restore that pg_dump in a PostgreSQL 10 or 11
4. Run ant update.database
  -> ERROR: local changes detected
TagsNo tags attached.
Attached Files

- Relationships [ Relation Graph ] [ Dependency Graph ]
blocks defect 0039516 closedalostale PG 10: false local changes positive after restoring PG 9.3 dump 

-  Notes
(0107566)
hgbot (developer)
2018-10-25 10:37

 Repository: erp/backports/3.0PR18Q4
Changeset: 10877055b912b7ab85a3783ebfed21b83b1f18ba
Author: Asier Lostalé <asier.lostale <at> openbravo.com>
Date: Wed Oct 24 10:31:04 2018 +0200
URL: http://code.openbravo.com/erp/backports/3.0PR18Q4/rev/10877055b912b7ab85a3783ebfed21b83b1f18ba [^]

fixed bug 39520: false local changes positive restoring PG 9.3 dump on PG 10

  After restoring in PG 10 a DB dump taken in PG 9.3, first update.database run
  incorrectly detects local changes.

  This was caused by many new functions added in PG 10 to trigram extension, those
  functions were unnecessarily included in the model checksum used to check if
  there are local changes.

  Now those functions are excluded: as dbsm only supports plsql functions, we now
  filter out all the ones implemented by binary code, which is how typically
  extension functions are implemented.

---
M src-db/database/model/prescript-PostgreSql.sql
---
(0107634)
caristu (viewer)
2018-10-29 11:22

 Reviewed

- Issue History
Date Modified Username Field Change
2018-10-24 10:22 alostale Type defect => backport
2018-10-24 10:22 alostale Target Version => 3.0PR18Q4.1
2018-10-24 10:22 alostale Target Version 3.0PR18Q4.1 => 3.0PR18Q4
2018-10-25 10:37 hgbot Checkin
2018-10-25 10:37 hgbot Note Added: 0107566
2018-10-25 10:37 hgbot Status scheduled => resolved
2018-10-25 10:37 hgbot Resolution open => fixed
2018-10-25 10:37 hgbot Fixed in SCM revision => http://code.openbravo.com/erp/backports/3.0PR18Q4/rev/10877055b912b7ab85a3783ebfed21b83b1f18ba [^]
2018-10-29 11:22 caristu Note Added: 0107634
2018-10-29 11:22 caristu Status resolved => closed
2018-10-29 11:22 caristu Fixed in Version => 3.0PR18Q4

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker