Dear All,
thanks for all the replies, yes, I tested it and it works. I am
deploying it now on 2 machines and my set up is like the:
server A is a VPS with OpenVPN server (this server has a Public IP)
which will be used for all people that are not local to the remote office
server B is a VM machine with OpenVPN client that will be located in
the remote office and using the delegator sequence-id_prefix to avoid
the collisions in the primary keys.
The two machines use the bdr extension from 2nd quadrant with Postgresql
9.4 with bdr enabled in both machines.
I will keep testing and report back.
On 1/21/2017 5:04 AM, Jacques Le Roux wrote:
Le 21/01/2017 à 08:58, Nicolas Malin a écrit :
Hi Bahaa, for your sequence pb like spot jacques and I thhink you
already ready the delegator prefix save your pb on all creation
|<delegator name=||"default"| |entity-model-reader=||"main"|
|entity-group-reader=||"main"| |entity-eca-reader=||"main"|
|||distributed-cache-clear-enabled=||"false"|
|sequenced-id-prefix=||"A"||>|
|||<group-map group-name=||"org.ofbiz"|
|datasource-name=||"localpostgres"||/>|
|||<group-map group-name=||"org.ofbiz.olap"|
|datasource-name=||"localpostgres"||/>|
|</delegator>|
Le 17/01/2017 à 17:15, Bahaa Alamood a écrit :
[...] I have a questions regarding the sync. So i have a scenario
as an example where one user on one server changes a record and I
have another user on another server changed the same record. would
the system be able to handle this when they sync? will I see both
changes as history?
As most case the sync analyze the last updateDate and the newer win.
Nicolas
Yes, thanks Nicolas
Since it's not done simultaneously and ms count collisions should not
happen
Jacques
