| From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
|---|---|
| To: | Keith Worthington <KeithW(at)NarrowPathInc(dot)com> |
| Cc: | PostgreSQL Novice <pgsql-novice(at)postgresql(dot)org> |
| Subject: | Re: protecting a database |
| Date: | 2006-08-24 11:40:12 |
| Message-ID: | 20060824114012.GA6605@wolff.to |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
On Wed, Aug 23, 2006 at 14:39:01 -0400,
Keith Worthington <KeithW(at)NarrowPathInc(dot)com> wrote:
> Is there a way to protect a database so that the structure cannot be seen?
Not if it is running on computers you don't control.
> 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.
Host the data on servers you control.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Fuhr | 2006-08-24 11:48:38 | Re: postgresql wildcard when parameter is -1 |
| Previous Message | Michael Meskes | 2006-08-24 09:11:20 | Re: Shared Objects (Dynamic loading) |