> > OO in PostgreSQL means that you can create own operators, datetypes,
> functions...
>
> Last I checked, all of these things were part of the SQL spec. I believe our
> only "OO" functionality is inheritance ... which I have yet to find a use
> for.
Can you tell me what the SQL99 spec sa
On Fri, 2002-06-28 at 03:21, Josh Berkus wrote:
>
> Karel,
>
> >
> > OO in PostgreSQL means that you can create own operators, datetypes,
> functions...
>
> Last I checked, all of these things were part of the SQL spec. I believe our
> only "OO" functionality is inheritance ...
Actually
> Last I checked, all of these things were part of the SQL spec. I believe
our
> only "OO" functionality is inheritance ... which I have yet to find a use
> for.
Well, it's lower maintenance than the 14-clause SELECT...UNION...UNION...
I'd have to write for ``correct'' code, in my current pro
Karel,
>
> OO in PostgreSQL means that you can create own operators, datetypes,
functions...
Last I checked, all of these things were part of the SQL spec. I believe our
only "OO" functionality is inheritance ... which I have yet to find a use
for.
Of course, I agree with Fabian Pascal,
On Thu, Jun 27, 2002 at 10:13:26AM +0530, Nishkala wrote:
>
> I am a student doing my graduation in India. I want to know what are the
> other OODBMS features ( other than inheritance ) available
> in PostGreSQL. It would be great if you can help me out with some
> information regarding this.
I am a student doing my graduation in India. I want to know what are the
other OODBMS features ( other than inheritance ) available
in PostGreSQL. It would be great if you can help me out with some
information regarding this.
Thanks,
Nishkala
--
Being yourself in the world which is constan
