Skip site navigation (1) Skip section navigation (2)

Re: OO future

From: Karel Zak <zakkr(at)zf(dot)jcu(dot)cz>
To: Hannu Krosing <hannu(at)tm(dot)ee>
Cc: pgsql-hackers <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: OO future
Date: 2002-10-30 08:51:34
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Wed, Oct 30, 2002 at 08:35:09AM +0200, Hannu Krosing wrote:
> >  Comments? I nothinig found about OO in the current TODO.
> I'm writing a small proposal for evoving inheritance and other OO
> features in 7.4 and beyond. Will post once 7.3 is out.

 Good! I look forward.

> > BTW, my
> >  examples are only small part of possible OO features, the others
> >  ideas are for example define PRIVATE/PUBLIC attributes in composite
> >  types
> At least the "Third Manifesto" by Date claims that PRIVATE/PUBLIC
> is better left to standard access control mechanisms (GRANT/REVOKE). 
> I agree to that.

 Yes, but it expect access control pre-column and for per composite type
 attribute. I understand PRIVATE as some internal data for methods
 and it needn't a speciffic access control, because control must be
 define for methods, and other way access PRIVATE data is not possible.
 IMHO it's better.
 The other important thing is possibility create table from type: 
 CREATE TABLE adresses AS address_t;

> > and methods, "SELECT FROM person p WHERE>tax() > 100;"
> The methods will probably have problems with syntax clashes with
> existing stuff.

 Hmm, ?


 Karel Zak  <zakkr(at)zf(dot)jcu(dot)cz>
 C, PostgreSQL, PHP, WWW,,

In response to

pgsql-hackers by date

Next:From: Tommi MaekitaloDate: 2002-10-30 09:03:34
Subject: tabcompletition and schema
Previous:From: Dave PageDate: 2002-10-30 08:19:11
Subject: Re: pgAdmin III (Was: Request for supported platforms)

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group