Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!ames!pasteur!helios.ee.lbl.gov!nosc!cod!dberg
From: dberg@cod.NOSC.MIL (David I. Berg)
Newsgroups: comp.databases
Subject: Re: Restricting access to Informix tables
Message-ID: <1548@cod.NOSC.MIL>
Date: 7 Jun 89 01:05:05 GMT
References: <1080@investor.UUCP> <1092@altos86.UUCP> <1347@infmx.UUCP> <585@tiamat.fsc.com>
Organization: Naval Ocean Systems Center, San Diego
Lines: 14

In article <585@tiamat.fsc.com>, jim@tiamat.fsc.com (Jim O'Connor) writes:
> But how do you keep the user from running "isql" and then tinkering with
> the data that they have access to with any arbitrary RDSQL statement.

With controlled access to isql -- i.e., owner and group access only. 
(In my case, the users know not of the existence of isql or what to do
with it.  The DBAs access the databases remotely whenever isql work must
be done.)

-- 
David I. Berg (dberg@nosc.mil)
GENISYS Information Systems, Inc., 4250 Pacific Hwy #118, San Diego, CA 92110
MILNET: dberg@nosc.mil
UUCP:   {akgua decvax dcdwest ucbvax}!sdcsvax!noscvax!dberg