Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!cica!tut.cis.ohio-state.edu!ucbvax!hplabs!hpl-opus!hpspdra!hpcmsrb!iverson
From: iverson@hpcmsrb.HP.COM (Kim Iverson)
Newsgroups: comp.databases
Subject: Re: Informix Isql Protection
Message-ID: <70220002@hpcmsrb.HP.COM>
Date: 16 Aug 89 19:24:26 GMT
References: <4266@uhccux.uhcc.hawaii.edu>
Organization: HP Corporate Manufacturing Systems
Lines: 17


Hi again,

I would like to correct a mistake in my earlier reply regarding
restricting access to tables using views.  I thought it would
be possible have the authorizations on the view override those
on the underlying table, but that isn't so.

So, although the view idea (especially in conjunction with the USER
idea from reply 2) may be useful in your case, I see no way to
GUARANTEE your students' confidentiality using Informix security
features, if that's your aim.

I was happy to learn about the USER variable, it's something
I can put to good use.

Kim Iverson