Re: Money casting too liberal? - Mailing list pgsql-general

From Jeff Davis
Subject Re: Money casting too liberal?
Date
Msg-id 1364603030.1187.220.camel@sussancws0025
Whole thread Raw
In response to Re: Money casting too liberal?  ("D'Arcy J.M. Cain" <darcy@druid.net>)
Responses Re: Money casting too liberal?
List pgsql-general
On Fri, 2013-03-29 at 16:30 -0400, D'Arcy J.M. Cain wrote:
> How would this be an issue?  If you are assigning a literal to a column
> then that's no issue.  Otherwise, a literal is simply a value that can
> be cast depending on the situation.  The money type is no different in
> that regard.
>
> As a result of an expression, it will have the type of the data in the
> expression.  What if the result is the addition of two columns of
> different precisions?  Pick the higher precision?  Forbid the
> operation?  The latter may make sense.  How can you add Yen and US$?

Why not have various rounding functions that do exactly what you want?
Then you can use them anywhere you want in an expression.

Tying a bunch of magic to the column, I/O function, or type system just
seems like the wrong approach when it comes to real differences (like
precision).

Regards,
    Jeff Davis



pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: unique indices without pg_constraint rows
Next
From: Gavan Schneider
Date:
Subject: Re: Money casting too liberal?