Re: pre-proposal: permissions made easier - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: pre-proposal: permissions made easier
Date
Msg-id 4A4988E3.3000702@agliodbs.com
Whole thread Raw
In response to Re: pre-proposal: permissions made easier  (Greg Stark <gsstark@mit.edu>)
Responses Re: pre-proposal: permissions made easier  (Greg Stark <gsstark@mit.edu>)
List pgsql-hackers
Greg,

> Well I don't understand how you get them wrong if you're just pasting
> them from a file. I mean, sure you can pick the wrong template but
> nothing can help you there. You could just as easily pick the wrong
> template if it's a database feature instead of a text file.

I really have to wonder if you've ever managed a production database 
project.

As someone who has managed quite a few, my idea of the feature is 
designed to make my life (and my clients') easier.  It's *vastly* easier 
to tell developers "don't touch the permissions, it will take care of 
itself" and set it in a central location than to expect them to remember 
to apply a set of permissions each time, or follow them around playing 
catch-up on the objects they add and modify.

Oracle, MSSQL, etc. all have management solutions for this.  For a good 
reason.

> "Agile" doesn't mean doing things without thinking about them :)

In many companies it does.  :-(

-- 
Josh Berkus
PostgreSQL Experts Inc.
www.pgexperts.com


pgsql-hackers by date:

Previous
From: Greg Stark
Date:
Subject: Re: pre-proposal: permissions made easier
Next
From: Robert Haas
Date:
Subject: autogenerating headers & bki stuff