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

From: Vikram A <vikkiatbipl(at)yahoo(dot)in>
To: David Johnston <polobo(at)yahoo(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: ncoding "Table Name" and "Filed Name"
Date: 2011-06-18 07:01:10
Message-ID: 765297.36126.qm@web137412.mail.in.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi Mr. David,

Thanks for the comment. I understood, its more difficult to mange the schema; when schema itself written in jig jack. 
Vikram

________________________________
From: David Johnston <polobo(at)yahoo(dot)com>
To: 'Vikram A' <vikkiatbipl(at)yahoo(dot)in>
Cc: pgsql-general(at)postgresql(dot)org
Sent: Friday, 17 June 2011 7:00 PM
Subject: RE: [GENERAL] ncoding "Table Name" and "Filed Name"

 
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

Browse pgsql-general by date

  From Date Subject
Next Message Greg Smith 2011-06-18 07:22:41 Re: Another RAID controller recommendation question
Previous Message David Boreham 2011-06-18 06:46:54 Another RAID controller recommendation question