| From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | "Roberts, Jon" <Jon(dot)Roberts(at)asurion(dot)com> |
| Cc: | "David Fetter" <david(at)fetter(dot)org>, "Jonathan Bond-Caron" <jbondc(at)openmv(dot)com>, "Harald Armin Massa" <haraldarminmassa(at)gmail(dot)com>, "Postgres General List" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Oracle and Postgresql |
| Date: | 2008-09-15 19:56:07 |
| Message-ID: | dcc563d10809151256g1f60ccc9y7b207fbe7956e21b@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-www |
On Mon, Sep 15, 2008 at 1:16 PM, Roberts, Jon <Jon(dot)Roberts(at)asurion(dot)com> wrote:
> In Oracle, you must be granted the ability to see someone's PL/SQL code.
> Secondly, you can "wrap" the code so no one can read it which protects
> the intellectual property aspect. I'm far less interested in protecting
> intellectual property because I'm not in that business. I am much more
> interested in meeting business needs which means securing not only the
> data in the database but also the code users write.
I could totally get behind needing permission to see the plpgsql code.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2008-09-15 19:58:44 | Re: Oracle and Postgresql |
| Previous Message | justin | 2008-09-15 19:53:39 | Re: Oracle and Postgresql |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2008-09-15 19:58:44 | Re: Oracle and Postgresql |
| Previous Message | justin | 2008-09-15 19:53:39 | Re: Oracle and Postgresql |