On Fri, Aug 31, 2001 at 10:15:59AM -0400, Mitch Vincent wrote:
> > said database once it is deployed on their machine? A large part of what
> > makes my application proprietary is the data model in the database, and
> > sure the database is bulletproof before I can begin deployment.
>
> If the people that have your application have physical access (or even
> remote superuser access) to the machine on which the database resides then
> there is little you could do to prevent a knowledgeable person from getting
> anything he/she wanted from the database, circumventing the PostgreSQL
And as a note, this is not limited to PostgreSQL either. The same
reasoning applies to Oracle, DB2, MS-SQL, and so on.
However, you may consider this: some people view proprietary data models
like this as a negative thing, not a positive one.
Many times we've had to reverse engineer the data storage stuff because the
provided interface simply did not provide enough flexibility to accomplish
what was needed. For those that had everything documented, those
enhancements went MUCH faster and much smoother. For those that were
"hidden," life was hell. And often those products were dropped.
mrc
--
Mike Castle dalgoda@ix.netcom.com www.netcom.com/~dalgoda/
We are all of us living in the shadow of Manhattan. -- Watchmen
fatal ("You are in a maze of twisty compiler features, all different"); -- gcc
