From: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
---|---|
To: | Shridhar Daithankar <shridhar_daithankar(at)persistent(dot)co(dot)in> |
Cc: | Jochem van Dieten <jochemd(at)oli(dot)tudelft(dot)nl>, <pgsql-advocacy(at)postgresql(dot)org> |
Subject: | Re: PostgreSQL vs. Oracle |
Date: | 2003-07-22 17:08:47 |
Message-ID: | Pine.LNX.4.33.0307221107340.19504-100000@css120.ihs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy |
On Tue, 22 Jul 2003, Shridhar Daithankar wrote:
> On 21 Jul 2003 at 22:35, Jochem van Dieten wrote:
>
> > Shridhar Daithankar wrote:
> > >
> > > e.g. Virtual private database? What is that? Unless I know what to expect out
> > > of that functionality, how can anybody offer an opinion or material on that?
> > >
> > > A link explaining what is virtual private database would be great there. Like
> > > http://www.oracle-base.com/Articles/8i/VirtualPrivateDatabases(VPD).asp.
> >
> > *That* is called a Virtual Private Database? It is just a fancy
> > way to do row level security on a single table in the database.
> > That article should be called "How to fake an updateable view
> > with check option.".
>
> Well, no matter how you and me thinks this is not very relevant or of any
> practical use, tons of people use it/will use it because oracle offers it to
> them.
>
> Sigh... there are quite a lot of things that are not ideal. Definition of ideal
> is one of them..:-)
Reading that page, it looks to me as if VPD are just schema sections with
security applied. I.e. Postgresql can do that.
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Treat | 2003-07-22 17:13:18 | Re: 7.4 Press Release -- Draft #3 |
Previous Message | Josh Berkus | 2003-07-22 16:56:02 | Re: 7.4 Press Release -- Draft #3 |