How to Update Caché User Full Name field via SQL?

Question

Question

Ben Spead · Jun 5, 2018

#Access control #SQL #Caché

Does anyone have any sample code for updating Caché users (and specifically Full Name and Comments) via SQL?

Bonus points for knowing specifically what security resource needs to be assigned to allow someone to run the SQL.

Thanks in Advance!

Ben

Discussion (9)1

Log in or sign up to continue

Gilberto Junior · Jun 5, 2018

Hi.

Use this code in namespace %sys:

update Security.Users set FullName = 'GOKU', Comment= 'Oi eu sou o GOKU' where id = 'gsjunior'

where the ID is the user login

1 0

score 0 · Answer 1 · 2018-06-05T21:16:02-04:00

Thank you Gilberto!

Any idea what resource is required to do this? Is it just granting UPDATE rights on the Security.Users table? Or is there a DB Role (limited - not %All or something crazy like that) which will allow this to be run?

Ben

score 0 · Answer 2 · 2018-06-05T21:25:51-04:00

Gilberto Junior · Jun 5, 2018

Hi Benjamin.

What is your need?

Are you implementing a tool for this?

0 0

score 0 · Answer 3 · 2018-06-05T22:01:47-04:00

This is for an exercise I'm creating for updating users via SQL. It is for educational purposes only and isn't going to be anything used in production

score 0 · Answer 4 · 2018-06-05T22:10:50-04:00

ok just be careful with this table so do not kill all users.

I recommend a backup of the file \ mgr \ CACHE.DAT responsible for storing users in Caché

score 0 · Answer 5 · 2018-06-05T22:20:20-04:00

Agreed - this could be very dangerous if not used carefully. Fortunately in my case it's a training VM where all users are created programmatically :)

Do you have any idea on the minimum privileges required to select or update the Security.User table?

Thanks again for your help!

score 1 · Answer 6 · 2018-06-05T22:48:58-04:00

I did not find the feature however I was able to do this by giving permission for updatena table Security.Users through the SQL Tables tab.

If you want to do this for a group you can create a Resource custon and release it.

score 0 · Answer 7 · 2018-06-05T22:50:34-04:00

thank you for the time you took to look! I thought that UPDATE SQL rights might be sufficient.

Thanks again and have a great night!

score 1 · Answer 8 · 2018-06-08T17:56:58-04:00

While Gilberto's answer is right, I would file this under "not the purpose of SQL". While there are many things you can do with SQL, the purpose of SQL is not to administer Caché/IRIS users. You are much better off using the Management Portal or one of the accepted APIs.