Peter Eisentraut <[EMAIL PROTECTED]> writes:
> On Thursday 11 December 2008 17:09:25 Tom Lane wrote:
>> I think there should be only *one* underlying column and that it should
>> be manipulable by either SQL commands or selinux. Â Otherwise you're
>> making a lie of the primary argument for having the SQL feature at all.
> Well, an SQL-manipulated row security column will probably have a content like
> {joe=rw/bob,staff=r/bob}
> An SELinux-aware row security column will probably have a content like
> blah_t:foo_t:quux_t
> And a Solaris TX-aware security column will probably have a content like
> Classified
> How can we stick all of these in the same column at the same time?
Why would we want to? I think one column that can hold any of these
ought to be sufficient. I certainly don't care for the idea that we
might invent still a third column for Solaris TX at some future time.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
