| From: | Ken Johanson <pg-user(at)kensystem(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Strict-typing benefits/costs |
| Date: | 2008-02-15 23:11:19 |
| Message-ID: | 47B61C17.2040803@kensystem.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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)?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2008-02-15 23:25:37 | Re: Approaches for Lookup values (codes) in OLTP application |
| Previous Message | Ken Johanson | 2008-02-15 23:08:15 | Re: Strict-typing benefits/costs |