Re: Limiting the operations that client-side code can perform upon its database backend's artifacts - Mailing list pgsql-general

From Peter J. Holzer
Subject Re: Limiting the operations that client-side code can perform upon its database backend's artifacts
Date
Msg-id 20220930184515.mw2avsox5daz6yok@hjp.at
Whole thread Raw
In response to Re: Limiting the operations that client-side code can perform upon its database backend's artifacts  (Bryn Llewellyn <bryn@yugabyte.com>)
Responses Re: Limiting the operations that client-side code can perform upon its database backend's artifacts  (Bryn Llewellyn <bryn@yugabyte.com>)
List pgsql-general
On 2022-09-29 20:24:59 -0700, Bryn Llewellyn wrote:
> Paraphrasing Peter, the design of the application's RDBMS backend has to
> implement its own notions of roles and privileges as a new layer on top of
> whatever the native RDBMS mechanisms provide. Some RDBMSs have native
> primitives that help the implementation of this next, application-specific,
> roles-and-privileges regime.

Can you provide a link to documentation (hopefully high-level
and concise) of such a system? I'm having a hard time imagining one
which I wouldn't either classify as "database roles by another name" or
"just data".

        hp

--
   _  | Peter J. Holzer    | Story must make more sense than reality.
|_|_) |                    |
| |   | hjp@hjp.at         |    -- Charles Stross, "Creative writing
__/   | http://www.hjp.at/ |       challenge!"

Attachment

pgsql-general by date:

Previous
From: Rickson Marshall
Date:
Subject: RE: Postgresql database and application server compatibility
Next
From: Igor Korot
Date:
Subject: Re: Is there Postgres ODBC binary for OSX?