Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0004740Openbravo ERPY. DBSourceManagerpublic2008-08-28 13:202008-12-18 12:43
rafaroda 
marvintm 
normalmajoralways
newopen 
20Ubuntu 7.10
 
 
Core
No
0004740: Revisions comparison mismatch in export.database
When working with Openbravo code, one can make commits that do not have to do with the database but that increment the source code revision. If one, wants then to export the database, he can not.
1) Commit a Java file.
2) Perform an export.database
Revisions comparisons when calling export.database should happen at a 'database' level, i.e., dbsourcemanager should look at the revision of 'database' folder not at the revision of the whole project.

In addition, different database exporting tasks should look at the revision number of their corresponding folders:
* export.database -> sourcedata and model folders revisions
* export.database.structure -> model folder revision
* export.database.data -> sourcedata folder revision
* expor.database.masterdata -> masterdata folder revision
* export.database.sampledata -> sampledata folder revision
dbsm_migrate, ToBeReviewed
Issue History
2008-08-28 13:20rafarodaNew Issue
2008-11-26 17:13pjuvaraTag Attached: ToBeReviewed
2008-11-27 12:35iperdomoNote Added: 0010770
2008-12-18 12:38jpabloaeSticky IssueNo => Yes
2008-12-18 12:39jpabloaeSticky IssueYes => No
2008-12-18 12:39jpabloaeTag Attached: dbsm_migrate
2008-12-18 12:41jpabloaeProject@4@ => Openbravo ERP
2008-12-18 12:41jpabloaeCategory => Y. DBSourceManager
2008-12-18 12:43jpabloaeAssigned To => marvintm

Notes
(0010770)
iperdomo   
2008-11-27 12:35   
Just FYI:
If you make a commit, you need to execute svn update after the commit to update the revision number on your working copy. I think that this only happens on command line users.