Hi Frank,
I understand a little bit of that part. I am in no way an expert but I will
tell you what I understand.
Say a user has ---
prefName1=prefValue1
prefName2=prefValue2
In this case, prefName1 and prefName2 will be stored in PREFS_PROPERTY_KEY
and prefValue1 and prefValue2 will be stored in PREFS_PROPERTY_VALUE.
I have found that I will be able to live with this much knowledge because I
can store my preferences in these tables, and I can retrieve them in my
portlet.
Hope that helps,
Amit
Original Message Follows
From: "Frank Villarreal" <[EMAIL PROTECTED]>
Reply-To: "Jetspeed Users List"
To: "Jetspeed Users List"
Subject: Why use Preferences for storing User Attributes?
Date: Wed, 9 Mar 2005 15:01:18 -0600
Hello all.
As I'm trying to integrate a legacy user database with J2's "SPI", I'm
discovering all sorts of, shall we say ... stumbling blocks :-). I do
understand the premise of how a User's attributes are accessed through the
Request object ... however, I'm finding it incredibly unintuitive to
decipher the J2 database structure (specifically user attribute instance
values). Can someone please explain to me the purposes of the following
specific tables ... and how they store user attribute values?
- PREFERENCE_VALUE
- PREFS_NODE
- PREFS_NODE_PROPERTY_KEY
- PREFS_PROPERTY_KEY
- PREFS_PROPERTY_VALUE
I have noted that the table "USER_ATTRIBUTE" stores the dynamic attribute
names, but I'm trying to figure out how to "store instances" of attributes
for individual users. Additionally, I do have a few "non-standard"
attribute fields I'd like to store for each user ... and have no idea (from
reading the docs or examining the DB model) of how to accomplish this.
Any reason as to why a simple USER_ATTRIBUTE_VALUE table wasn't used
instead? Being that a web site "User" is one of the central objects in a
portal, seems to me that it would be best if customization of this aspect
were kept simple? Just my 2 cents.
Any insight would be greatly appreciated.
- Frank
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
