#1 is okay if you are sure the size and scope of your user attributes will never grow beyond the size of the description field and you don’t care to use the description field for a variable length description.
#3 is a non-starter because it means you potentially eliminate the ability of upgrading MarkLogic to new revisions. #2 is what we've done in the past, but I am curious about other suggestions. -Keith ______________________________________________________________________________________________________ On Tue, Sep 27, 2011 at 1:20 PM, [email protected] <[email protected]>wrote: > If we want to add custom properties or attributes to a user account in > MarkLogic (beyond username and description), it seems like we have the > following options: > > 1. Put the values in the description field tokenized (Bob | Accounting | > 555-1223 | [email protected]) > 2. Use a separate XML file in the content database > 3. Add properties to the XML file for the user in the Security DB > > #1 is good except there is a limit to the number of characters. #2 adds the > overhead of making sure the Securty DB and "extended user info" XML files in > the content DB are always in sync. #3 starts tinkering with the Security DB > which sounds like something to avoid. > > I'm hoping there are other options. What do you all recommend? > > thanks, > Ryan > > > _______________________________________________ > General mailing list > [email protected] > http://developer.marklogic.com/mailman/listinfo/general > > -- Keith "Do what you can, with what you have, where you are." - Theodore Roosevelt
_______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
