Re: make == as = ?

Fabien COELHO wrote:

> If you want to promote postgreSQL, then it should be good that anything
> from outside (whether standard or not) can work with postgreSQL, but
> anything that work in pg may not work outside;-)

I couldn't disagree more. What you are asking for is to do whatever (you
think) gets the crowds cheering. That is exactly what MySQL attempts by
stuffing one half baked feature after another into their db product and
calling it "integration". What we try instead is to create a stable,
reliable and predictable database server.

> Also, if I add some new operators in pg_operator, say && for AND, I'm not
> sure the optimiser will know that is a AND and take that into account.

AND is not an operator, it is a keyword in the first place. And the
optimiser can use a multi-column index containing a user defined data
type here, so it is well aware of the things you add, if you do it right.

Jan

--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #