| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | André Fernandes <andre(dot)de(dot)camargo(dot)fernandes(at)hotmail(dot)com> |
| Cc: | robertmhaas(at)gmail(dot)com, heikki(dot)linnakangas(at)enterprisedb(dot)com, arhipov(at)dc(dot)baikal(dot)ru, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Name column |
| Date: | 2010-09-24 15:43:54 |
| Message-ID: | 5224.1285343034@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
=?iso-8859-1?B?QW5kcukgRmVybmFuZGVz?= <andre(dot)de(dot)camargo(dot)fernandes(at)hotmail(dot)com> writes:
>> On Fri, Sep 24, 2010 at 6:35 AM, Heikki Linnakangas
>> <heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
>> I'm starting to wonder if we should think about deprecating this
>> behavior. It is awfully confusing and unintuitive.
> I agree, it is very unintuitive.
> +1 for deprecating this behavior.
-1. There's nothing wrong with the function-as-a-computed-column
feature, and it seems likely that taking it away will break applications.
What we are getting bit by is that I/O coercions to string types can be
specified this way. Maybe what we ought to do is remove just that one
capability. It'd be a bit non-orthogonal, but seems fairly unlikely to
break anything, especially since we only began to allow such things
recently (in 8.4 looks like).
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-09-24 15:48:15 | Re: Name column |
| Previous Message | Tom Lane | 2010-09-24 15:33:25 | Re: Re: [BUGS] BUG #5650: Postgres service showing as stopped when in fact it is running |