From: | "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> |
---|---|
To: | "'Mike Arace'" <mikearace(at)hotmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Deployment of PostgreSQL Applications |
Date: | 2001-08-31 16:47:59 |
Message-ID: | 3705826352029646A3E91C53F7189E32016762@sectorbase2.sectorbase.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> 1) Is it legal to bundle Postgresql with another commercial
> application,
> assuming the database will have to be significantly
> reconfigured and tuned?
> (at the application level, not the source code level) I read
> over the
> licenses I could find on the site and they seemed to imply
> that the answer
> was yes, but I'd like to reaffirm that.
Yes.
> 2) More importantly, is it possible to prevent a customer
> from peeking into
> 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 it'd
> be tough to maintain a competative edge when everyone can see
> exactly how I
> do things in the database by logging into their postgres
> account, adding
> some users and changing permissions on their machine. I
> really need to make
> sure the database is bulletproof before I can begin deployment.
No way.
Vadim
From | Date | Subject | |
---|---|---|---|
Next Message | Shaun Thomas | 2001-08-31 16:48:56 | Re: Regarding Vacuumdb |
Previous Message | Mikheev, Vadim | 2001-08-31 16:45:49 | Re: getting the oid for a new tuple in a BEFORE trigger |