Re: Strict-typing benefits/costs

Tom Lane wrote:
>
> It's possible to special-case any particular function you really feel
> you need this behavior for.  We did special-case || (the string
> concatenation operator), and there was some discussion of also putting
> in a built-in special case for LIKE, but we desisted from sliding any
> further down that slippery slope.  Since it's possible for users to
> install such hacks for themselves, as in the example here,
> http://archives.postgresql.org/pgsql-general/2007-11/msg00538.php
> there didn't seem to be a convincing case for weakening the type
> checking for everybody.
>

Tom, is it accurate to assume that newer PG versions will further
tighten type-strictness (say, '2008-01-01' presently being comparable to
a datetime)? Also, do you know of any other vendors that are heading in
this direction (removing by default the autocasts)?