hi, Natan, LSC-users. after reading what Natan suggested and finding out the magic in PostgreSQL's "STRING_AGG(<table.column>, <separator>)", I only had to change the SQL query to obtain *gratifying results* in my test environment.
I will come back to you if any problem arises when moving to production-like data. many thanks for your precious help, roberto benedetti ----- Original Message ----- > > Hi Roberto, I will try to answer you > > > > [1] could you provide pointers to a working (and detailed/production > ready/dumb-free) example? - I can pay for that ;-) > > You can simply read the multivalued custom attribute inserting it on > <fetchedAttributes> tag. LSC will concatenate it and put the result > on the destination > > [1-bis] could you please confirm that "concatenation" is the only > supported model? could you please anyway provide a complete working > example? (it might be worth providing it in the sample-* dir) > > Yes, a synch from LDAP read a multivalued attribute and joins it in a > single valued string delimited by a separator that can be global or > specific for that attribute > > > The global one is defined by > > > <defaultDelimiter>|</defaultDelimiter> <!-- delimiter for multivalued > fileds read on a single value string --> > > inside <propertiesBasedSyncOptions> > > [2] /suppose/ we have 10K users, 10 custom multi-valued attributes > and hourly based syncs. would LSC's concatenation fit our needs? > > > > You should not have any issue on an hourly based synch. > > > > > On Mon, Apr 11, 2016 at 9:09 PM, Roberto Benedetti < > [email protected] > wrote: > > > hello to everyone. > > I landed on lsc-project just a week or so ago and, since then, I > tried to figure out the way to let your software feed our > multi-purpose/multi-tenant system. > > then I started testing with a simplified version of our data and - > unexpectedly referred to my usual luck __and__ ability - everything > worked properly. > > moving from the basic single-valued attribute model, I tried to get > closer to our production data introducing multi-valued attributes > (in our home-made/service-oriented object classes, we defined some > of them (e.g. to apply (user|group)-based RADIUS ACLs)). > that's where I encountered problems that made a shy guy become a > POSTer. > > > > */finally/ the question* - I'm not sure that I won't ask anymore! > > > I could only find hints in historical lsc-* list-archives. > is separator+concatenation+javascript the only way to get rid of > multi-valued attributes? > > [1] could you provide pointers to a working (and detailed/production > ready/dumb-free) example? - I can pay for that ;-) > > [1-bis] could you please confirm that "concatenation" is the only > supported model? could you please anyway provide a complete working > example? (it might be worth providing it in the sample-* dir) > > > [2] /suppose/ we have 10K users, 10 custom multi-valued attributes > and hourly based syncs. would LSC's concatenation fit our needs? > > > thanks for your support, > roberto benedetti > > > > > _______________________________________________________________ > Ldap Synchronization Connector (LSC) - http://lsc-project.org > > lsc-users mailing list > [email protected] > http://lists.lsc-project.org/listinfo/lsc-users > > _______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-users
