ExtendedData versus UserData column

We are interested in storing additional data in our livelink system. We know that an option is to use ExtendedData column from DTREE table as it is described in SDK course but we also would like to know if it is possible to use UserData column from KUAF table.Does it exist any preference to one of them according to technical reasons?All comments will be well receivedThanks

Find more posts tagged with

Comments

eLink User

Message from Dylan Wright via eLinkit all depends on what kind of data you're wanting to store. useextendeddata to store node information (categories and attributes are betterfor this), use KUAF if you want to store USER-speficic settings.> -----Original Message-----> From: eLink Discussion: Development Discussion> [mailto:development@elinkkc.opentext.com]> Sent: Tuesday, January 30, 2001 9:51 AM> To: eLink Recipient> Subject: ExtendedData versus UserData column>>> ExtendedData versus UserData column> Posted by CentrisaAdmin on 01/30/2001 12:47 PM>> We are interested in storing additional data in our livelink> system. We know that an option is to use ExtendedData column from> DTREE table as it is described in SDK course but we also would> like to know if it is possible to use UserData column from KUAF table.> Does it exist any preference to one of them according to> technical reasons?> All comments will be well received>> Thanks>> [To reply to this thread, use your normal e-mail reply function.]>> ============================================================>> Discussion: Development Discussion> https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objI> d=786303&objAction=view>> Livelink Server:> https://knowledge.opentext.com/knowledge/livelink.exe>>>

eLink User

Message from Hans Stoop via eLinkFor user specific data you can either use UserDate or the kuafprefstable.If you use userdata, for compatability reasons you can best complywith the following scheme1. If the content of the field is empty:Add an assoc with as key the name of your ospace/module. Store yourdata in the key field.2. If the field contains a assoc:Add a key with the name of your ospace/module to the assoc. Store yourdata in the key field. Leave the other data untouched.3. If the field contains something else as an assoc:Add an assoc with as key the name of your ospace/module. Store yourdata in the key field. Store the original data as another key in theassoc.This way it will stay compatible with Livelink Directory Services andeall other customizations that follow this rule.Hans Stoop--------------Consultant Partner Programs Europehstoop@opentext.com+31 23 5652333http://www.opentext.com/> -----Original Message-----> From: eLink Discussion: Development Discussion> [mailto:development@elinkkc.opentext.com]> Sent: dinsdag 30 januari 2001 18:57> To: eLink Recipient> Subject: RE ExtendedData versus UserData column>>> RE ExtendedData versus UserData column> Posted by eLink on 01/30/2001 12:56 PM>> Message from Dylan Wright via eLink>> it all depends on what kind of data you're wanting to store. use> extendeddata to store node information (categories and> attributes are better> for this), use KUAF if you want to store USER-speficic settings.>> > -----Original Message-----> > From: eLink Discussion: Development Discussion> > [mailto:development@elinkkc.opentext.com]> > Sent: Tuesday, January 30, 2001 9:51 AM> > To: eLink Recipient> > Subject: ExtendedData versus UserData column> >> >> > ExtendedData versus UserData column> > Posted by CentrisaAdmin on 01/30/2001 12:47 PM> >> > We are interested in storing additional data in our livelink> > system. We know that an option is to use ExtendedData column from> > DTREE table as it is described in SDK course but we also would> > like to know if it is possible to use UserData column> from KUAF table.> > Does it exist any preference to one of them according to> > technical reasons?> > All comments will be well received> >> > Thanks> >> > [To reply to this thread, use your normal e-mail reply function.]> >> > ============================================================> >> > Discussion: Development Discussion> > https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objI> > d=786303&objAction=view> >> > Livelink Server:> > https://knowledge.opentext.com/knowledge/livelink.exe> >> >> >>> [To reply to this thread, use your normal e-mail reply function.]>> ============================================================>> Topic: ExtendedData versus UserData column> https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=2439073&objAction=viewDiscussion: Development Discussionhttps://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=786303&objAction=viewLivelink Server:https://knowledge.opentext.com/knowledge/livelink.exe