| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: proposal: early casting in plpgsql |
| Date: | 2009-05-28 18:12:39 |
| Message-ID: | 14013.1243534359@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
> I propose for types with typmod -1 early casting - etc casting to
> target type on planner level. We cannot use this method for defined
> typmod, because we would to raise exception for following situation:
What existing coding habits will this break? People have long been
accustomed to use plpgsql for end-runs around SQL casting behavior,
so I'm not really convinced by the idea that "make it more like SQL"
is automatically a good thing.
Also, it seems bizarre and inconsistent that it would work one way
for variables with a typmod and an entirely different way for those
without. How will you explain that to users who never heard of a
typmod?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2009-05-28 18:27:01 | Re: search_path vs extensions |
| Previous Message | Tom Lane | 2009-05-28 17:54:03 | Re: PostgreSQL Developer meeting minutes up |