0039970: Unique constraint on obei_entity_synchronization needs to include synchronization_applicant column

Description

The obei_entity_synchronization table currently has a unique constraint by ad_client_id and obei_entity_mapping_id.

This unique constraint should take into account the synchronization_applicant column. Otherwise it will not be possible to store different synchronizations per synchronization_applicant for the same client and entity mapping.

Steps To Reproduce

In description

Tags

No tags attached.

Attached Files

Relationships [ Relation Graph ] [ Dependency Graph ]

Notes
(0108985) hgbot (developer) 2019-01-17 09:01	Repository: erp/pmods/org.openbravo.service.external.integration Changeset: 7e2039d7fb46d6f7f5bee253a8d2fab3517a522a Author: Carlos Aristu <carlos.aristu <at> openbravo.com> Date: Thu Jan 17 08:59:53 2019 +0100 URL: http://code.openbravo.com/erp/pmods/org.openbravo.service.external.integration/rev/7e2039d7fb46d6f7f5bee253a8d2fab3517a522a [^] fixes bug 39970: Include synchronization_applicant column in unique constraint --- M src-db/database/model/tables/OBEI_ENTITY_SYNCHRONIZATION.xml ---

(0109074) AugustoMauch (manager) 2019-01-22 13:13	Code reviewed and verified

Issue History
Date Modified	Username	Field	Change
2019-01-17 08:47	caristu	New Issue
2019-01-17 08:47	caristu	Assigned To	=> caristu
2019-01-17 08:47	caristu	Review Assigned To	=> AugustoMauch
2019-01-17 09:01	hgbot	Checkin
2019-01-17 09:01	hgbot	Note Added: 0108985
2019-01-17 09:01	hgbot	Status	new => resolved
2019-01-17 09:01	hgbot	Resolution	open => fixed
2019-01-17 09:01	hgbot	Fixed in SCM revision	=> http://code.openbravo.com/erp/pmods/org.openbravo.service.external.integration/rev/7e2039d7fb46d6f7f5bee253a8d2fab3517a522a [^]
2019-01-22 13:13	AugustoMauch	Note Added: 0109074
2019-01-22 13:13	AugustoMauch	Status	resolved => closed