Re: ncoding "Table Name" and "Filed Name"

From: "David Johnston" <polobo(at)yahoo(dot)com>
To: "'Vikram A'" <vikkiatbipl(at)yahoo(dot)in>
Cc: <pgsql-general(at)postgresql(dot)org>
Subject: Re: ncoding "Table Name" and "Filed Name"
Date: 2011-06-17 13:30:27
Message-ID: 001d01cc2cf2$b9307450$2b915cf0$@yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

We are expecting following advantages through this,

Unauthorized use either by the

1. DB administrator

2. ex-developer Or

3. Any body

This why PostgreSQL has the concept of "ROLE"s.

The data, not the schema, is what needs to be secured.you are not preventing
unauthorized use only making both it and authorized use more difficult. It
isn't that hard to get the database to tell you all the table and field
names then it is just a matter of issuing a "SELECT * FROM .." to
see/retrieve the data.

A rose is a rose by any other name.

For the people you do trust you are making them jump through lots of hoops
in order to work with the schema.

David J.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Kevin Grittner 2011-06-17 13:55:22 Re: Postgres 8.3.10 Alter Table Waiting issue
Previous Message Diogo Santos 2011-06-17 11:04:27 Auto Start second postgresql instance MAC OS X