Subject | Re: [ib-support] Role/permission question |
---|---|
Author | Helen Borrie |
Post date | 2002-02-11T11:15:55Z |
At 11:49 AM 11-02-02 +0100, Svein wrote:
Then you can call up the view, passing the user name as WHERE criterion, thus limiting each users view to those columns and rows to which it is authorised.
...
WHERE UserName = USER...
or
WHERE UserName = CURRENT_USER (Firebird only)
Both USER and CURRENT_USER are available to DSQL and procedures in Firebird.
cheers,
Helen
All for Open and Open for All
Firebird Open SQL Database ยท http://firebirdsql.org
_______________________________________________________
>Hidayat,If you have a lot of users and each one has its own set of rows, store the user name for identification instead of a digit. That way, you can have a view defined consisting of the two columns in question plus the user name.
>I guess you could define one view for each user and give him/her
>select/update rights for just one of them. But it isn't a good solution if
>you have hundreds of users and you may be better off using stored
>procedures (I hope there is a variable called CURRENT_USER, but I don't know).
Then you can call up the view, passing the user name as WHERE criterion, thus limiting each users view to those columns and rows to which it is authorised.
...
WHERE UserName = USER...
or
WHERE UserName = CURRENT_USER (Firebird only)
Both USER and CURRENT_USER are available to DSQL and procedures in Firebird.
cheers,
Helen
All for Open and Open for All
Firebird Open SQL Database ยท http://firebirdsql.org
_______________________________________________________