| From: | Ken Johanson <pg-user(at)kensystem(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Strict-typing benefits/costs |
| Date: | 2008-02-15 23:08:15 |
| Message-ID: | 47B61B5F.90008@kensystem.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Jeff Davis wrote:
> If postgresql were to revert to 8.2 implicit casting behavior, would
> that actually improve compatibility with other DBMSs? Every DBMS
> probably has it's own rules for implicit casting, different from every
> other DBMS.
>
> So are you sure it wouldn't just introduce more compatibility problems
> somewhere else? Or worse, it could hide the problems during
> migration/testing, and they could surface after you put it into
> production.
In my opinion the autocasting behaviors of the database are probably
more consistent and fined tuned, than their explicit cast function. Or
in the least, they may actually *save* mistakes that (lay) programmers
would make (by adding casts for the sake of PG).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ken Johanson | 2008-02-15 23:11:19 | Re: Strict-typing benefits/costs |
| Previous Message | Gregory Stark | 2008-02-15 22:12:58 | Re: Why isn't an index being used when selecting a distinct value? |