Re: Inconsistent or incomplete behavior obverse in where

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: pogden(at)claresco(dot)com, pgsql-sql(at)postgresql(dot)org
Subject: Re: Inconsistent or incomplete behavior obverse in where
Date: 2002-11-12 19:13:09
Message-ID: 200211121113.09365.josh@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-sql


Paul,

> Thanks for the reply. Much of what you say is as we expected.
> I see that 7.3 has addressed the "Unable to identify an operator
> '=' for types 'numeric' and 'double precision'" problem, but
> I'm not sure how. Context-sensitive approach? Overloaded operator
> approach? Something else ( is there )?

A modification of the operators available.

> If the release of 7.3 is soon, perhaps we can get by with the
> band-aid approach of overloading the comparison operators
> until such time as the new version is available. Production
> for us is next spring, so maybe we'll be okay on this one.
> This approach would certainly allow our development team to
> right their code one way.

7.3 final is expected before December.

--
-Josh Berkus

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Curtis Faith 2002-11-12 19:41:40 Prepare enabled pgbench
Previous Message Marc G. Fournier 2002-11-12 18:58:17 ecpg "problem" ...

Browse pgsql-sql by date

  From Date Subject
Next Message Martin Crundall 2002-11-12 20:12:55 Re: Postgres Date pg_dump/Import:
Previous Message Paul Ogden 2002-11-12 18:52:20 Re: Inconsistent or incomplete behavior obverse in where