0034777: Make dataset/synchronized table extendable

Openbravo Issue Tracking System - Retail Modules

View Issue Details

Project

Category

View Status

Date Submitted

Last Update

0034777

Retail Modules

StoreServer

public

2016-12-19 21:08

2017-01-18 17:22

Reporter

mtaal

Assigned To

AugustoMauch

Priority

normal

Severity

minor

Reproducibility

have not tried

Status

closed

Resolution

no change required

Platform

OS Version

Product Version

Target Version

RR17Q2

Fixed in Version

Merge Request Status

Review Assigned To

OBNetwork customer

Support ticket

Regression level

Regression date

Regression introduced in release

Regression introduced by commit

Triggers an Emergency Pack

Summary

0034777: Make dataset/synchronized table extendable

Description

There are sometimes cases where a module only wants to replace a single datasettable or synchronized table definition. This next to adding new definitions.

Openbravo does not easily support replacing artifacts from another module. In case of dataset/synchronized table this can be handy to allow using custom columns for filtering out specific records.

Steps To Reproduce

See description

Proposed Solution

To support overrides in datasettable an approach can be to add a column to datasettable to point to the replaced datasettable. The dataset table export logic should then for a datasettable if it got replaced and if so then use the replacing dataset.

For synchronized table the same approach can be used. But the synchronized table has a unique index on the table. An alternative approach is to add 'override' support in java using a custom extension which is called always at every sync (from example from the base client router) and which can adapt/change the list of nodes to which the a data change is replicated.

Additional Information