We could also discuss another idea: Using the record's timestamp for generating a graph of sync entities is tricky. We need pretty precise system clock ntp sync and cpu time for ofbiz to generate the graph.
Another approach might be to implement triggers in entity engine ( if that feature does not exist already ) and create a transaction log. I use the same approach but on a DB level - using DB triggers. The clients remember the last ID of the transaction log entry they have successfully reached so they just ask the server - give me everything after it. The transaction log approach would eliminate the system clock issues and graph generation. -- deyan -----Original Message----- From: Deyan Tsvetanov <[email protected]> Reply-to: [email protected] To: Jacques Le Roux <[email protected]> Cc: [email protected] Subject: Re: Entity Sync Date: Wed, 28 Oct 2009 09:31:01 +0200 Yup, we all thank you :) I'll send you my entity sync setup and some notes and stuff i've discovered by the end of the week. In general it can be re-worked a bit and still be a very useful tool so users can choose whether to use it or use some db level synchronization. -- Deyan -----Original Message----- From: Jacques Le Roux <[email protected]> Reply-to: "Jacques Le Roux" <[email protected]> To: [email protected] Subject: Re: Entity Sync Date: Tue, 27 Oct 2009 21:05:51 +0100 From: "David E Jones" <[email protected]> > That's great Jacques, I'm glad someone is coordinating and looking into > things with it. I appreciate the compliment, I have no escape now ;o) Jacques > -David > > > On Oct 27, 2009, at 1:22 PM, Jacques Le Roux wrote: > >> Marc David, >> >> Sounds like David took the time to read you message... >> >> I remains, that we need to clarify what is working and what is not. I >> should work on this these next days. >> >> Jacques >> >> From: "David E Jones" <[email protected]> >>> >>> Marc, >>> >>> Actually this is a separate topic from what I've seen in the other >>> thread. It would be good to read the other thread, but I'd >>> recommend taking everything there with a grain of salt. There seems to be >>> some misunderstanding in a lot of the assessments >>> of what the Entity Sync does and what the issues are with it (ie things >>> that make it slow, the constraints it has trying to >>> reproduce time order of database changes over multiple tables, etc). >>> >>> In any case, yes, it is correct that the current Entity Sync stuff does >>> not have filtering on a record level (other than by >>> time), and also has nothing to follow a graph of related records to >>> include desired information. >>> >>> -David >>> >>> >>> On Oct 27, 2009, at 8:24 AM, Marc Morin wrote: >>> >>>> Rookie error... apologies >>>> >>>> ----- Original Message ----- >>>> From: "Jacques Le Roux" <[email protected]> >>>> To: [email protected] >>>> Sent: Tuesday, October 27, 2009 9:36:50 AM GMT -05:00 US/Canada Eastern >>>> Subject: Re: Entity Sync >>>> >>>> Hi Marc, >>>> >>>> Did you follow recent threads on this subject ? >>>> >>>> Jacques >>>> >>>> From: "Marc Morin" <[email protected]> >>>>> We have a couple of use cases where we need to sync a subset of the >>>>> information in one database and mirror it into another. >>>>> >>>>> Been looking at the entity sync capability that is present in ofbiz. >>>>> Very good start, ability to build a sync set that is a >>>>> collection of entities to sync (pull or push) between delegators (or >>>>> service). >>>>> >>>>> In my case, I need to create the nest of entities to consider for the >>>>> sync, but I need to restrict the rows from some >>>>> starting >>>>> point. >>>>> >>>>> Use case 1: Want to import a collection of parties from one system >>>>> along with their relationships between the set of parties >>>>> and >>>>> their contact info, notes, preferences, etc.... >>>>> >>>>> Use case 2: Create a product category, rollups, and then associate >>>>> products to that category. Want to publish this >>>>> category, >>>>> products, and subset of pricing, product content, features, etc.... to >>>>> other instances. >>>>> >>>>> Looks like a modification to entity sync is required to do this? or am >>>>> i mistaken. >>>>> >>>>> Modification involves: >>>>> >>>>> - build set of entities in sync group >>>>> - add condition restrictions on possibly any number of entities for >>>>> candidate rows. (category_id = 'x') >>>>> - "soft" inclusion by foreign key reference from a row in the set to >>>>> one that is not explicit. >>>>> - alter row for foreign key references outside of entity set to null or >>>>> to rows that cannot be replicated. >>>>> >>>>> >>>>> I'm sure more precision is needed here and will to do the work. Just >>>>> wanted to see if others have similar use cases and if >>>>> so, >>>>> what they have done. >>>>> >>>>> Marc Morin >>>>> Emforium Group Inc. >>>>> ALL-IN Software™ >>>>> 519-772-6824 ext 201 >>>>> [email protected] >>>>> >>>>> >>>>> >>>> >>>> >>> >> >> > >
