Re: Write Access, but not Read access?

"Tibor Karaszi" <tibor_not_pressed_ham_.karaszi_at_cornerstone.se> wrote in message news:<zM9F9.6787$1r1.273785_at_newsc.telia.net>...
> Don't want that person to read information entered by someone else, perhaps?
>
> --
> Tibor Karaszi
>
>
> "Tookelso" <Tookelso_at_yahoo.com> wrote in message
> news:5a63818d.0211270917.75cc84a7_at_posting.google.com...
> > I encountered a situation where our DB Admins set up an account with
> > insert/delete/update access to a database, but not read access.
> >
> > It was for an application which loaded data into a database.
> >
> > Can anyone see a reason for being this stringent with permissions?
> >
> > I've never encountered this type of permission setup before. I would
> > assume that if they can zap / update / insert data, then why not read
> > it?
> >
> > Thoughts, anyone?
> >
> > --Took

Sounds unlikely to me that the application will be able to update or delete data in the database if it's not allowed to read the information.

In practice this permission would probably turn out to be insert only permission. Received on Fri Nov 29 2002 - 13:27:26 CET