Skip site navigation (1) Skip section navigation (2)

Re: protecting a database

From: "Andrej Ricnik-Bay" <andrej(dot)groups(at)gmail(dot)com>
To: KeithW(at)narrowpathinc(dot)com, "pgsql-novice(at)postgresql(dot)org" <pgsql-novice(at)postgresql(dot)org>
Subject: Re: protecting a database
Date: 2006-08-23 19:19:59
Message-ID: b35603930608231219h6aaefdafj4007d155eaeeaea2@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-novice
On 8/24/06, Keith Worthington <KeithW(at)narrowpathinc(dot)com> wrote:
> Hi All,
>
> Is there a way to protect a database so that the structure cannot be seen?
>
> I would like to use postgresql for data storage in a product I am
> working on.  The challenge is that most of the value of the product will
> be in the database structure itself (data model, functions, etc.).  I
> want to prevent people from seeing anything while still allowing the GUI
> to get at the data.
>
> Is there a way to do this?  URLs to relevant documentation are welcome.
I don't think you can - not via postgres-means, anyway.

If you think about it - the server process needs to be able
to access those structures;  if they were munged it couldn't.

> --
>
> Kind Regards,
> Keith

Cheers,
Andrej



-- 
Please don't top post, and don't use HTML e-Mail :}  Make your quotes concise.

http://www.american.edu/econ/notes/htmlmail.htm

In response to

pgsql-novice by date

Next:From: Don MorrisonDate: 2006-08-23 19:48:53
Subject: Re: Conditional INSERT: if not exists
Previous:From: Franck RoutierDate: 2006-08-23 18:57:55
Subject: Re: Conditional INSERT: if not exists

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group