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 tried2009-12-09 17:142009-12-11 06:38
ReportermarvintmView Statuspublic 
Assigned Tomarvintm 
PrioritynormalResolutionfixedFixed in Version
StatusclosedFix in branchFixed in SCM revision22091b0e5d61
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Web browser
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo

0011712: ad_db_modified function found structure changes in the database when there had been no change

DescriptionThe ad_db_modified function (which is used in update.database and export.database to find out if there were changes in the database structure) didn't work correctly when the database was exported in a .dmp file and imported in a new database.

Specifically, it found changes even if no change had been done.
Steps To ReproduceCreate the database (install.source, update.database, ...).
Check that you can do update.database without problems (=you don't get the -Dforce error).
Export the database to a dmp file.
Import it again in a new database. Change your file so that it points to this new database.
Do update.database again. It will fail because it finds "differences" in the new database, although it's identical to the old one.
Proposed SolutionThe function needs to be fixed.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
hgbot (developer)
2009-12-09 17:16

Repository: erp/devel/pi
Changeset: 22091b0e5d61bc1952872a0d3538637c1ecc9f60
Author: Antonio Moreno <antonio.moreno <at>>
Date: Wed Dec 09 17:15:57 2009 +0100
URL: [^]

Fixed issue 11712. Function will now work even if you export/import the whole database.

M src-db/database/model/prescript-PostgreSql.sql
shuehner (administrator)
2009-12-10 14:11

tested, checksum checks still works fine (detects not change) after dumping and recreating the database on postgres using both plain and custom backup-format.
hudsonbot (developer)
2009-12-11 06:35

A changeset related to this issue has passed a series of tests and has been promoted to main:

Changeset: [^]
Tests: [^]
hudsonbot (developer)
2009-12-11 06:38

An OBX is generated including a changeset related to this issue and is available at:

OBX: [^]

- Issue History
Date Modified Username Field Change
2009-12-09 17:14 marvintm New Issue
2009-12-09 17:14 marvintm Assigned To => marvintm
2009-12-09 17:16 hgbot Checkin
2009-12-09 17:16 hgbot Note Added: 0022596
2009-12-09 17:16 hgbot Status new => resolved
2009-12-09 17:16 hgbot Resolution open => fixed
2009-12-09 17:16 hgbot Fixed in SCM revision => [^]
2009-12-10 14:11 shuehner Note Added: 0022641
2009-12-10 14:11 shuehner Status resolved => closed
2009-12-11 00:00 anonymous sf_bug_id 0 => 2912328
2009-12-11 06:35 hudsonbot Checkin
2009-12-11 06:35 hudsonbot Note Added: 0022671
2009-12-11 06:38 hudsonbot Checkin
2009-12-11 06:38 hudsonbot Note Added: 0022678

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker