On Jun 14, 2011, at 4:01 PM, Magnolia Forums (on behalf of Dennis Rieks) wrote:
> > Hi, > > thank you all! > > We need to automaticly create and sync ~40.000 Users from a mysql database. > Manual adding roles/users is not needed, so i think im going to add an > dms_acl entry to every user node for access to the users home directory. Just make sure that you test what happen when you update such user and that the entry is not removed by default Magnolia User Dialog. > Has anyone of you experience with adding so much entrys to dms? It is better > to use a structure like this? > /home/a/ap/applejuice > /home/r/ra/rabbit > /home/r/ri/richard > /home/r/ri/rieks Hierarchy will definitively work better. You should never try to exceed more then 1000 nodes at the same level (siblings). The repository would be able to handle it, but retrieving and updating nodes would be slower then if they are properly spread like you show above. In one of the 2.x versions JackRabbit introduced the tool that can create such hierarchies automatically and hide them from the user so everything appears to be flat and fast at a same time :) ... but your Magnolia is most likely not running on JR 2.x yet so you need to create those yourself. UserManager itself should not have any issues with the hieararchies. Just out of interest, did you also thought about writing your own user manager or even a login module and keeping those users external as they are? HTH, Jan > > Thanks, > Dennis > > -- > Context is everything: > http://forum.magnolia-cms.com/forum/thread.html?threadId=77b19d8f-ff53-49cd-bd72-7809c5395bc6 > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
