nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

LLAttrData table

Kristy_Shen

Hi:Does anyone know how the LLAttrData table gets populated? Does it have to do with categories?I currently have a query that checks for data in this table with DefID=4827 and AttrID=3, 4, 5, 12, 13, 14. I'm not sure what the numbers mean and why it would query for those specific values.

Find more posts tagged with

Comments

Bhupinder_Singh

Message from Bhupinder Singh <bsingh@opentext.com> via eLink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">eLink

The schema indicates that the LLAttrData table contains [category] attribute data for objects in "row per value" format. In this regards, the Livelink 9.0.0 release notes indicate:

"Database Schema

In order to realize rapid data retrieval and provide support for interactive SQL query, the attribute data is stored in two tables. The first table — LLAttrBlobData — is for storing attribute data in blob format (in 10K chunks) and the second table — LLAttrData — is for storing attribute data in 'row per value' format."

The purpose of LLAttrData is to allow customers to write reports against category attribute data using SQL. The use of LLAttrBlobData by Livelink is one of the reasons we do not approve of direct inserts into LLAttrData, because such inserts will not result in updates to LLAttrBlobData which is the actual table used by Livelink for retrieval of category data for presentation in the Livelink interface.

For schema explanation of categories and attributes, please see pages 30-34 of the Livelink 9.0.0 release notes located here:

https://knowledge.opentext.com/go/2352432

You can use the "?func=attributes.dump" request handler to get a table that shows the relationship between DefID, AttrID, etc. for categories in your system. If your Livelink URL looks like:http://singhdellsr/live91sp3/livelink.exe?func=llworkspace...you would need to change it to:http://singhdellsr/live91sp3/livelink.exe?func=attributes.dump

Let me know if that helps...

- Bhupinder----------------------------------------------
Bhupinder Singh, B.Math, B.Ed.
Senior Systems Analyst, Information Technology
Open Text, Waterloo, Ontario, Canada
----------------------------------------------

From: eLink Discussion: Development Discussion [mailto:development@elinkkc.opentext.com]
Sent: Wednesday, November 12, 2008 9:21 AM
To: eLink Recipient
Subject: LLAttrData table

LLAttrData table

Posted by kristyshen (Shen, Kristy) on 11/12/2008 09:20 AM

Hi:

Does anyone know how the LLAttrData table gets populated? Does it have to do with categories?
I currently have a query that checks for data in this table with DefID=4827 and AttrID=3, 4, 5, 12, 13, 14.

I'm not sure what the numbers mean and why it would query for those specific values.

Kristy_Shen

Wow! That reply came back in warp speed! Thanks so much Bhupinder! You're always so helpful :DKristy

Kristy_Shen

Hi Bhupinder:I just have one more question. Is there any way to set the DefID to specific number for a category? Or is this set by the system and not modifiable?Kristy

Appu_Nair

My $0.02Nothing in livelink should be alterd by sql updates because all the referential integrity of associated tables are done by callback functions.While saying this I have actually updated tables with probably no ill effects (but pensive moments)defid in llattrdata is dataid in dtree .All cats have subtype=131This dtree.dataid is a system allocated number why would you want to change it ?

Bhupinder_Singh

Message from Bhupinder Singh <bsingh@opentext.com> via eLink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">eLink

As far as I know, the DefID is generated by Livelink and is not configurable. The DefID is a foreigh key to DTree.DataID, i.e. it corresponds to the DataID of the category object itself.

- Bhupinder

From: eLink Discussion: Development Discussion [mailto:development@elinkkc.opentext.com]
Sent: Wednesday, November 12, 2008 9:53 AM
To: eLink Recipient
Subject: LLAttrData table one more question

LLAttrData table one more question		Posted by kristyshen (Shen, Kristy) on 11/12/2008 09:50 AM
In reply to: RE LLAttrData table		Posted by bsingh (Singh, Bhupinder) on 11/12/2008 09:31 AM

Hi Bhupinder:

I just have one more question. Is there any way to set the DefID to specific number for a category? Or is this set by the system and not modifiable?

Kristy

Kristy_Shen

The reason is because we currently have a view (created by Global services as a part of a customization) that queries the LLAttData table and the Dtree table. It looks for the DefID=4287. After we migrated from 951 to 971, this value changed to 75293.Thus, I was wondering if there's an easy way to set that number so I wouldn't have to change the view.

Kristy_Shen

Ah, I see. That's why the id changed from the 951. I was hoping that it was more like a type value that would stay the same rather than dataid. Ok, I guess in that case, I have no choice but to update the view to query for the id.

Appu_Nair

AFAIK the dataid should not have changed with the upgrade.Very hard for me to digest that a 9.5 upgarde to 9.7 would cause a change.If you had used a migration utility this could be understandable

Kristy_Shen

Come to think of it, I should probably change the view to query for the category subtype (131) and the name "Correspondance" (which is the obj with DefID=4827) instead of the DefID. This way, if we keep the name of the category the same across multiple environments, we won't have to update the view everytime we move to a new environment. Do you have any other suggestions or insights into this issue?

Kristy_Shen

This is because we did a brand new install and added new data into the db rather than do a backup and restore of the existing database.

Appu_Nair

what is preventing somebody from creating "Correspondence" in multiple places other than the category volume or even catgory folders within the category volume.Being Devil's advocate

Kristy_Shen

The categories that has Def=4827 that we currently query for resides in the categories volume. Only administrators have access it. (we only add the required categories during deployment) So when I query for "correspondance" I will also include the subtype and the path to this particular category. (we will keep the path the same when we deploy the categories to each environment)Any categories with the same name created by users will have a different path. Category folders will have a different subtype.

Appu_Nair

that should work you have all your ducks in a row:)

John W. Simon, Jr.

You might want to consider performance implications before making this change. I know name is not indexed, but it might not be that big of a deal since you also included the subtype.Still, are you saying something like "select * from llattrdata where defid = (select dataid from dtree where subtype = 131 and name = 'Correspondance')"? I would guess that is quite a bit slower than "select * from llattrdata where defid = 4827". It's not like the ID is going to change that often!!!

Kristy_Shen

Thanks for the suggestion. See, the annoying thing is that some of our 971 envs are brand new installs and some are migrated from 951. Thus, if I use the id, I will need to user different versions of the view on different environments depending on whether it is a new install or a migrated one. (a migrated one would retain the 4827 but a new only would not)