-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, 21 Dec 2007 16:47:46 -0500
Andrew Sullivan <ajs@crankycanuck.ca> wrote:
> On Fri, Dec 21, 2007 at 04:19:51PM -0500, Tom Lane wrote:
> > > 2. Protect the content of a field from _some_ users on a
> > > given system,
> >
> > I would argue that (2) is reasonably well served today by setting up
> > separate databases for separate users.
>
> I thought actually this was one of the use-cases we were hearing.
> Different people using the same database (because the same data),
> with rules about the different staff being able to see this or that
> function body. I can easily imagine such a case, for instance, in a
> large organization with different departments and different
> responsibilities. It seems a shame that the only answer we have
> there is, "Give them different databases."
I think there is a fundamental disconnect here. The "Give them
different databases" argument is essentially useless. Consider a
organization that has Sales and HR.
You don't give both a separate database. They need access to "some" of
each others information. Just not all.
Sincerely,
Joshua D. Drake
- --
The PostgreSQL Company: Since 1997, http://www.commandprompt.com/
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
SELECT 'Training', 'Consulting' FROM vendor WHERE name = 'CMD'
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHbDkOATb/zqfZUUQRAqzmAJ9VhNXYtr/N7px3/iUenUJN+7r9jQCfQtj+
Hyfo4fLGrBGUN4jJcSgZEh0=
=xeLs
-----END PGP SIGNATURE-----