Re: Permission for not Django app to do Write and Read - Mailing list pgsql-general

From Luca Ferrari
Subject Re: Permission for not Django app to do Write and Read
Date
Msg-id CAKoxK+5G2MoNs23Ge52Eq4LP9dUN5X+hLDxjvr=26-+2JSNyLg@mail.gmail.com
Whole thread Raw
Responses Re: Permission for not Django app to do Write and Read
List pgsql-general
On Sat, Aug 24, 2019 at 11:53 AM Peter Wainaina <petwah17@gmail.com> wrote:
>
> Thanks much for the response. This is what I mean am a database administrator for a production company and the
productowner doesn't want me to be able to either read or write information that will come from Django application.
 

I personally hate this kind of setup, because it does not make any
sense to me that a developer must setup an application that must
interact with a database that the developer himself cannot interact
with.
However, keep it simple: define a django user, assign each object to
such user, revoke any permission from public.
And then let's the product owner setup a password.
Or look at pgcrypto, because the ony reliable way to deal with "don't
look at my data" setup is cryptography.

Luca



pgsql-general by date:

Previous
From: Thiemo Kellner
Date:
Subject: Re: timestamp out of range while casting return value to function'sreturn type
Next
From: Howard Wells
Date:
Subject: Postgres SQLSTATE[08006] [7] timeout expired