On 03/21/2013 11:34 AM, Adrian Klaver wrote:
> On 03/21/2013 07:52 AM, Michael Orlitzky wrote:
>> On 03/21/2013 10:39 AM, Adrian Klaver wrote:
This won't fly unfortunately. It's a shared host, and the "developers"
are a mixed bag of our employees, consultants, and the customer's
>>>
On 03/21/2013 07:52 AM, Michael Orlitzky wrote:
On 03/21/2013 10:39 AM, Adrian Klaver wrote:
This won't fly unfortunately. It's a shared host, and the "developers"
are a mixed bag of our employees, consultants, and the customer's employees.
Do not follow. The set role= is put on a login role.
On 03/21/2013 10:39 AM, Adrian Klaver wrote:
>>
>> This won't fly unfortunately. It's a shared host, and the "developers"
>> are a mixed bag of our employees, consultants, and the customer's employees.
>
> Do not follow. The set role= is put on a login role. It will only work
> on those databases
On 03/20/2013 08:57 PM, Michael Orlitzky wrote:
On 03/20/2013 08:05 PM, Adrian Klaver wrote:
Not sure why everything being owned by dev_user is a problem, you said
the developers don't care about permissions or want to deal with them so
why does it matter what role their objects get created as?
On 03/20/2013 08:05 PM, Adrian Klaver wrote:
>>
>> Now everything in the database will be owned by dev_user. But what
>> happens if we have 100 databases (this is realistic for us), and add a
>> new developer a year down the road? I have to not only add him to
>> dev_user, but look through each dat
On 03/20/2013 04:11 PM, Michael Orlitzky wrote:
On 03/20/2013 06:40 PM, Adrian Klaver wrote:
On 03/20/2013 03:26 PM, Michael Orlitzky wrote:
On 03/20/2013 05:18 PM, Rob Sargent wrote:
At the moment, everyone's just experimenting. Even with the proper
tooling, my blog app shouldn't have to h
On 03/20/2013 06:40 PM, Adrian Klaver wrote:
> On 03/20/2013 03:26 PM, Michael Orlitzky wrote:
>> On 03/20/2013 05:18 PM, Rob Sargent wrote:
>
>>
>> At the moment, everyone's just experimenting. Even with the proper
>> tooling, my blog app shouldn't have to handle the database permissions
>> table
On 03/20/2013 03:26 PM, Michael Orlitzky wrote:
On 03/20/2013 05:18 PM, Rob Sargent wrote:
At the moment, everyone's just experimenting. Even with the proper
tooling, my blog app shouldn't have to handle the database permissions
table-by-table. I should be able to set up sensible defaults.
On 03/20/2013 05:18 PM, Rob Sargent wrote:
> What's your process? First I've heard of a group of dev's ignorant of
> permission _and_ trusted to change things in a db which affect others.
It's a playground for a group of people. They want to be able to create
stuff, and then modify that stuff. N
On 03/20/2013 02:24 PM, Michael Orlitzky wrote:
On 03/20/2013 04:12 PM, Alvaro Herrera wrote:
Michael Orlitzky wrote:
I'm running into this exact situation:
http://www.postgresql.org/message-id/CAG1_KcBFM0e2buUG=o7ojq_ktadrzdgd45ju7gke3duz0sz...@mail.gmail.com
We really need to be able to hav
On 03/20/2013 04:12 PM, Alvaro Herrera wrote:
> Michael Orlitzky wrote:
>> I'm running into this exact situation:
>>
>> http://www.postgresql.org/message-id/CAG1_KcBFM0e2buUG=o7ojq_ktadrzdgd45ju7gke3duz0sz...@mail.gmail.com
>>
>> We really need to be able to have a group of developers who can creat
Michael Orlitzky wrote:
> I'm running into this exact situation:
>
> http://www.postgresql.org/message-id/CAG1_KcBFM0e2buUG=o7ojq_ktadrzdgd45ju7gke3duz0sz...@mail.gmail.com
>
> We really need to be able to have a group of developers who can create
> things and modify each others' stuff[1]. Is it
I'm running into this exact situation:
http://www.postgresql.org/message-id/CAG1_KcBFM0e2buUG=o7ojq_ktadrzdgd45ju7gke3duz0sz...@mail.gmail.com
We really need to be able to have a group of developers who can create
things and modify each others' stuff[1]. Is it still more or less
impossible?
The
13 matches
Mail list logo
