[Info-ingres] Whatever happened to...

[Roy Hann]

Karl Schendel wrote:

> I expect that most of the reason was [...] plus the notion
> that views would do more or less the same thing.

I hope that's not the notion, because you can't use views to get the
same effect that you get from this:

create accounts ( 
customer=char(5) not null, 
balance=decimal(6,2) not null, 
pin=char(4) not null ) \g

range of a is accounts 
define permit append, delete on a to roy \g

range of a is accounts
define permit retrieve on a(customer,balance) to roy \g
 
range of a is accounts
define permit replace on a(balance) to roy \g

A data-masking SQL view equivalent to the retrieve permit above is not
an updateable view so the user is forced to be aware that they select
from one "table" but insert into a different one, because the "table"
names are different.

And to impose the behaviour of the QUEL replace permit above you need an
SQL rule and procedure, which is--happily--invisible to the user, but
more tedious for the DBA to set up.

Roy