Tom Lane wrote:
> Aside from the semantic-gap issue, there is the point that providing
> a cast might actually mask application errors. I can well imagine
> cases where one of the reasons for using MONEY is *exactly* that it's
> not a plain number or easily convertible to one.
I'm always against casts, but I can hardly object to an explicit cast between
money and numeric.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
