> > this is a totally uninformed and inaccurate assessment ... the current
> > state of OO/OR features in PgSQL has been sitting pretty much on one
> > persons shoulders ... v7.0 has some extensions/fixes added in this arena,
> > and we would very much welcome anyone that wishes to work with us towards
> > further improvements on this ...
>
> it's not fair! It is understandable that you love PG, but it does not
> mean you can be blindly doing that!
>
> it is a plain fact that OR/OO features are not the focus in recent years,
> and some of them are broken or not work right, no mention of
> documentations.
> And, informix is certainly a better product in that regards! -- and I also
> emphasized the crucial advantage of PG that it is open source and people
> esp. master degree candidate can contribute and leave a good trail.
>
> -- Please tell me, why and where is this info is uninformed?!
We need to get our OR/OO stuff to be better supported and more polished.
It basically works, but when you layer arrays, rules, unions,
subqueries, and all the other stuff on top of it, it sometimes breaks.
--
Bruce Momjian | http://www.op.net/~candle
pgman@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
