> This could clearly be a KILLER APP/TYPE for us. This is a pretty
> sophisticated use of our type system. Indexing should present no
> problems. We supply the comparison routines and plug them in, and the
> optimizer automatically uses the indexes.
i'd like that to be true. but the section of the manual which describes
this isn't as clear as the examples (the COMPLEX type in particular) in
the contrib/ directory at the time i started the work. figuring out what
OID my comparison operators happened to get and plugging these values into
a PG_OPERATOR insert was just more than i could figure out how to automate.
other than the OID thing i really love the postgres type system, btw, and i
can't see why anybody would ever use MySQL (or Oracle) unless it has the
same feature.
