Missing permission statements
Tony Demeis asked why dbschema on IDS 7.31 omitted select permission statements for a new table. Art S. Kagel said only owner permissions exist by default and dbschema does not print them; his myschema utility does. Malc added the NODEFDAC variable and dbschema -p all. Mark D. Stock noted ANSI-mode databases grant no default permissions.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Hi,
Why is it that after I create a table in IDS 7.31 and then run dbschema on
the database the 'select' permissions statements at the end of the process
are not created for the new table. I've tried issuing a checkpoint but that
makes no difference. What must be done so that the database will recognize
the new table?
Thank you,
Tony
By
default the table has no permissions except owner permissions and dbschema
does not print out owner permissions. If you use my dbschema replacement
utility, myschema, it will print the owner permissions for the table so you can
see them. If you manually grant some additional permissions on the table to
another user those will show up in the dbschema output.
Myschema is part of the package utils2_ak available for download from the IIUG
Software Repository.
Art S. Kagel
----- Original Message -----
From: Tony Demeis <Tony.Demeis@moh.gov.on.ca>
At: 9/26 11:38
> Hi,
> Why is it that after I create a table in IDS 7.31 and then run dbschema on
> the database the 'select' permissions statements at the end of the process
> are not created for the new table. I've tried issuing a checkpoint but that
> makes no difference. What must be done so that the database will recognize
> the new table?
>
>
> Thank you,
> Tony
Not quite true - from IDS V7.31 there's the NODEFDAC environment variable -
set it to 1 and tables are created with no default permissions, otherwise
all users get all perms.
And if you use the "-p all" switch with dbschema you get to see perms for
the tables.
----- Original Message -----
From: "ART KAGEL, ...." <KAGEL@bloomberg.net>
To: <ids@iiug.org>
Sent: Friday, September 26, 2003 4:44 PM
Subject: Re: Missing permission statements [1939]
> By default the table has no permissions except owner permissions and
dbschema> does not print out owner permissions. If you use my dbschema replacement
> utility, myschema, it will print the owner permissions for the table so
you can
> see them. If you manually grant some additional permissions on the table
to
> another user those will show up in the dbschema output.
>
> Myschema is part of the package utils2_ak available for download from the
IIUG
> Software Repository.
>
> Art S. Kagel
>
> ----- Original Message -----
> From: Tony Demeis <Tony.Demeis@moh.gov.on.ca>
> At: 9/26 11:38
>
> > Hi,
> > Why is it that after I create a table in IDS 7.31 and then run dbschema
on
> > the database the 'select' permissions statements at the end of the
process
> > are not created for the new table. I've tried issuing a checkpoint but
that
> > makes no difference. What must be done so that the database will
recognize
> > the new table?
> >
> >
> > Thank you,
> > Tony
>
>
>
>
Malc wrote: > Not quite true - from IDS V7.31 there's the NODEFDAC environment variable - > set it to 1 and tables are created with no default permissions, otherwise > all users get all perms. Also, if you create a table in a MODE ANSI database, then the ANSI standard is no permissions by default. Cheers, -- Mark. +----------------------------------------------------------+-----------+ | Mark D. Stock mailto:mdstock@MydasSolutions.com |//////// /| | Mydas Solutions Ltd http://MydasSolutions.com |///// / //| | +-----------------------------------+//// / ///| | |We value your comments, which have |/// / ////| | |been recorded and automatically |// / /////| | |emailed back to us for our records.|/ ////////| +----------------------+-----------------------------------+-----------+