X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org
Received: from localhost (unknown [200.46.204.2])
	by svr1.postgresql.org (Postfix) with ESMTP id E2EE6D1CB1D
	for <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	Thu, 19 Feb 2004 16:47:41 +0000 (GMT)
Received: from svr1.postgresql.org ([200.46.204.71])
	by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024)
	with ESMTP id 28514-07
	for <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	Thu, 19 Feb 2004 12:47:34 -0400 (AST)
Received: from tht.net (vista.tht.net [216.126.88.2])
	by svr1.postgresql.org (Postfix) with ESMTP id D758FD1D25D
	for <pgsql-sql@postgresql.org>; Thu, 19 Feb 2004 12:47:33 -0400 (AST)
Received: from [134.22.70.180] (dyn-70-180.tor.dsl.tht.net [134.22.70.180])
	by tht.net (Postfix) with ESMTP
	id BFE4E76A47; Thu, 19 Feb 2004 11:47:35 -0500 (EST)
Subject: Re: Compiling pl/pgsql functions
From: Rod Taylor <rbt@rbt.ca>
To: Stephan Szabo <sszabo@megazone.bigpanda.com>
Cc: Rodrigo Sakai <rodrigo@2bfree.com.br>, pgsql-sql@postgresql.org
In-Reply-To: <20040219081426.D53888@megazone.bigpanda.com>
References: <20040219134412.27393.qmail@hm10.locaweb.com.br>
	<20040219081426.D53888@megazone.bigpanda.com>
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="=-i4243qXr6Q4iHC7nHzVu"
Message-Id: <1077209281.25444.91.camel@jester>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.5 
Date: Thu, 19 Feb 2004 11:48:02 -0500
X-Virus-Scanned: by amavisd-new at postgresql.org
X-Archive-Number: 200402/325
X-Sequence-Number: 17015

--=-i4243qXr6Q4iHC7nHzVu
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

> AFAIK there's not much you can do for obfuscation of pl functions right
> now since someone will be able to see the src text in pg_proc. However,
> are you allowing people that you don't want to see the code access to
> write arbitrary sql to the database?

This is another one of those items where it would be nice if users
didn't need access to read the system tables, but instead could rely on
the information schema (with extensions) to see what they own or have
access to use -- but nothing else.

Sometimes HR gets paranoid about billing seeing their business logic, or
lack thereof, but accounting needs to use both sets of information to do
their work.

Otherwise, having each group relegated to their own schema with
semi-public views is a nice way to pass information from department to
department for small companies. Sure beats the spreadsheets on the
central filer approach.

--=20
Rod Taylor <rbt [at] rbt [dot] ca>

Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
PGP Key: http://www.rbt.ca/signature.asc

--=-i4243qXr6Q4iHC7nHzVu
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)

iD8DBQBANOjB6DETLow6vwwRAs9uAJ9kvCENjs6FSlvxSz8vaUc87fj9DgCfUoDL
GCjQu6pWJxR/Ohvxvp0nvV8=
=QqC+
-----END PGP SIGNATURE-----

--=-i4243qXr6Q4iHC7nHzVu--