| From: | Samuel Gendler <sgendler(at)ideasculptor(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Carlos Mennens <carlos(dot)mennens(at)gmail(dot)com>, Viktor Bojović <viktor(dot)bojovic(at)gmail(dot)com>, "PostgreSQL (SQL)" <pgsql-sql(at)postgresql(dot)org> |
| Subject: | Re: Finding Max Value in a Row |
| Date: | 2012-05-14 05:45:10 |
| Message-ID: | CAEV0TzAZK6_J7g1V=3cE_BUpbOHsYDgrJe1pmwSi2+FeCu7YYQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
On Sun, May 13, 2012 at 8:11 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> It strikes me that "cannot be cast" is a poor choice of words here,
> since the types *can* be cast if you try. Would it be better if the
> message said "cannot be cast implicitly to type foo"? We could also
> consider a HINT mentioning use of USING.
>
Without the hint, I don't think that there's a ton of value in changing the
message as proposed. It's more accurate, so may be worth doing anyway, but
probably won't be much more helpful than the current message to someone who
hasn't encountered the problem before. If they've seen it before, the old
message is likely sufficient to remind them.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Trinath Somanchi | 2012-05-14 11:52:12 | Re: syncing - between databases |
| Previous Message | Steven Crandell | 2012-05-14 05:32:18 | Re: syncing - between databases |