"How things are broken" would also be an interesting topic :-). I had
developed a natural flair for it in my very early Remedy days - teaches you
a thing or two I tell you!

 

Joe

 

  _____  

From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of John Sundberg
Sent: Wednesday, February 20, 2013 1:20 PM
To: [email protected]
Subject: Re: T123 and User_Cache tables

 

** 

Doug,

 

Thanks for the explanation.

 

I always like to hear how things actually get made - or how the decisions
have come about.

 

So - a suggestion. I think it would be fun to have a WWRUG session on "how
it's made" for ARS.

 

Things like -- why the table numbers, why the required fields. to some --
that would be interesting history.

 

Thanks again,

 

-John

 

 

 

 

On Wed, Feb 20, 2013 at 12:07 PM, Mueller, Doug <[email protected]>
wrote:

** 

Yogesh,

 

The T123 table on your system is the database table for the User form.  This
is a data table just like any other

data table in the system for any form in the system.  This is just a data
table.  It does feed the User_Cache

table with a subset of the data in the table.  It is the User Interface if
you will of the User_Cache.

 

User_Cache is a system table that is used to hold the definitions of users
that are defined within the

AR System environment for authorization and authentication.  This is the
table actually used for security

checks and interaction within the system.

 

In the original design, we allowed for the User_Cache to be managed from
remote machines or

environments.  So, you could have a User form on one system updating a
User_Cache on the other.  This is

not a general practice in the current configuration of the system.

 

So, there is history here and some designs allowing for different options
for managing users.  But today, the

User_Cache is essentially a partial copy of the User form in almost every
configuration.

 

You should not worry about the User_Cache form.  You should not be manually
updating it or in fact

interacting with it in any way.  It is an internal management table.  There
are checksums on the data so if you

do manual manipulate it, it will invalidate entries (this is to prevent
people from changing rights or settings

to break system security).

 

I home this helps,

 

Doug Mueller

 

From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of Yogesh Ketkar
Sent: Wednesday, February 20, 2013 1:39 AM
To: [email protected]
Subject: T123 and User_Cache tables

 

** 

Hello,

 

I am relatively new to ARS. I just stumbled upon two tables in the schema
T123 ( obtained from the query select * from arschema where name = 'User')
and User_Cache. Both seem to contain more or less, same information about
users created in ARS. Table attached to user form looks to be T123. So the
question is what is table User_Cache doing?

 

Regards, Yogesh

 

_ARSlist: "Where the Answers Are" and have been for 20 years_

_ARSlist: "Where the Answers Are" and have been for 20 years_ 





 

-- 

John Sundberg

Kinetic Data, Inc.

"Your Business. Your Process."

 

Save The Date! Second Annual KEG (Kinetic Enthusiasts Group)

Feb. 25th - March 1st in Denver, CO. For more information click here -
<http://www.kineticdata.com/Events/KEG.html> KEG

 

651-556-0930 I [email protected] 

 <http://www.kineticdata.com/> www.kineticdata.com I
<http://community.kineticdata.com/> community.kineticdata.com 


_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Reply via email to