Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0016320Openbravo ERPA. Platformpublic2011-03-16 12:002011-06-10 17:48
ReporterioritzCia 
Assigned Tomarvintm 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOS20OS VersionUbuntu 10.04
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customerNo
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0016320: Failure ordering changes when exporting datasets.
DescriptionThe dataset exporting process creates some differences it should not have to.
Steps To Reproduce- Install Spanish Taxes https://code.openbravo.com/erp/mods/org.openbravo.localization.spain.referencedata.taxes/ [^]
- Create a client with name TAXES applying the dataset Spanish Taxes module supplies.
- Make some change in a tax of that dataset in that client.
- Export dataset.
- See that there are changes that there sould not be.

The attatched file shows the diff generated.
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
depends on backport 00167432.50MP32 closed marvintm Failure ordering changes when exporting datasets. 
related to defect 0015973 closed AugustoMauch ant export.sample.data gives distinct output in oracle than in postgresql 
Attached Filesdiff taxesDataset.diff (920,929) 2011-03-16 12:00
https://issues.openbravo.com/file_download.php?file_id=3692&type=bug
Issue History
Date ModifiedUsernameFieldChange
2011-03-16 12:00ioritzCiaNew Issue
2011-03-16 12:00ioritzCiaAssigned To => alostale
2011-03-16 12:00ioritzCiaFile Added: taxesDataset.diff
2011-03-16 12:00ioritzCiaModules => Core
2011-03-16 12:00ioritzCiaOBNetwork customer => No
2011-03-21 10:17alostaleStatusnew => scheduled
2011-03-21 10:17alostaleAssigned Toalostale => marvintm
2011-03-21 10:17alostalefix_in_branch => pi
2011-03-24 19:54hgbotCheckin
2011-03-24 19:54hgbotNote Added: 0035222
2011-03-24 19:54hgbotStatusscheduled => resolved
2011-03-24 19:54hgbotResolutionopen => fixed
2011-03-24 19:54hgbotFixed in SCM revision => http://code.openbravo.com/erp/devel/pi/rev/a488a723e6241de9a195bb4ab5ffaa22f959b46d [^]
2011-04-11 13:27dalsasuaNote Added: 0035816
2011-04-11 13:27dalsasuaStatusresolved => new
2011-04-11 13:27dalsasuaResolutionfixed => open
2011-04-11 13:27dalsasuaStatusnew => scheduled
2011-04-11 13:27dalsasuaStatusscheduled => resolved
2011-04-11 13:27dalsasuaResolutionopen => fixed
2011-06-10 17:48shuehnerNote Added: 0038261
2011-06-10 17:48shuehnerStatusresolved => closed
2011-07-14 15:18shuehnerRelationship addedrelated to 0015973

Notes
(0035222)
hgbot   
2011-03-24 19:54   
Repository: erp/devel/pi
Changeset: a488a723e6241de9a195bb4ab5ffaa22f959b46d
Author: Antonio Moreno <antonio.moreno <at> openbravo.com>
Date: Thu Mar 24 19:51:33 2011 +0100
URL: http://code.openbravo.com/erp/devel/pi/rev/a488a723e6241de9a195bb4ab5ffaa22f959b46d [^]

Fixed issue 16320. Datasets shouldn't have formal changes when reexported.
Two changes have been made:
- Children BaseOBObjects will be sorted in the same way as their parents already were.
- List properties will now be generated with a defined order, as the Entities will now be created following a defined order

---
M src/org/openbravo/base/model/ModelProvider.java
M src/org/openbravo/dal/xml/EntityXMLConverter.java
---
(0035816)
dalsasua   
2011-04-11 13:27   
A backport is required
(0038261)
shuehner   
2011-06-10 17:48   
Reviewed/tested on pi-mp0 (rev: 8ab3332cfb89). Changeset change ordering of all rows inside a dataset once on next export. But after this one change the new order is stable and not changing row-ordering on each unrelated change in the dataset.
Technically also entity initialization in dal-startup is modified. However the new order is table and sensible (ordered by table-name and not unknown/internal-hashcode). -> Fine also -> Closing