Quoting Bruno Wolff III <[EMAIL PROTECTED]>:
> On Mon, Jan 05, 2004 at 11:32:42 +0500,
> Michael Gill <[EMAIL PROTECTED]> wrote:
> >
> > I think I have found the simple solution by separating the user from the
> > owner of the tables, however!
> >
> > I have simply created tables and function
On Mon, Jan 05, 2004 at 11:32:42 +0500,
Michael Gill <[EMAIL PROTECTED]> wrote:
>
> I think I have found the simple solution by separating the user from the
> owner of the tables, however!
>
> I have simply created tables and functions in the owner's schema(A),
> then granted execution to the
Andrew Dunstan wrote:
Michael Gill said:
Hello,
I've tried asking this question elsewhere and have not received a
satisfactory response.
I want to restrict users of my packaged database from directly
accessing the data or reading the schema. I would provide access to
the read-on
Michael Gill said:
> Hello,
>
> I've tried asking this question elsewhere and have not received a
> satisfactory response.
>
> I want to restrict users of my packaged database from directly
> accessing the data or reading the schema. I would provide access to
> the read-only data through function
Hello,
I've tried asking this question elsewhere and have not received a
satisfactory response.
I want to restrict users of my packaged database from directly accessing
the data or reading the schema. I would provide access to the read-only
data through functions (which works well in PG). I fi
