>> Is there any reason why the backend doesn't cast an unquoted integer
>> to
>> a boolean value?
>
> Hidden cross-category typecasts are evil. I'd accept this as an
> explicit cast ('e' in pg_cast) but not automatic.
>
> Also, what about the other direction? Providing a cast in only one
> direction is pretty inconsistent.
test=> SELECT 1::BOOL, 0::BOOL, TRUE::INT4, FALSE::INT4;
bool | bool | int4 | int4
------+------+------+------
t | f | 1 | 0
(1 row)
Okey doke, both directions are now provided and the cast has to be
explicit. -sc
--
Sean Chittenden
