Re: Implicit coercions need to be reined in

From: "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Barry Lind" <barry(at)xythos(dot)com>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Implicit coercions need to be reined in
Date: 2002-04-16 18:38:08
Message-ID: 46C15C39FEB2C44BA555E356FBCD6FA4961DAF@m0114.s-mxs.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> I suspect that the main thing that will cause issues is removal of
> implicit coercions to text. For example, in 7.2 and before you can do
>
> test72=# select 'At the tone, the time will be ' || now();
> ?column?
> -------------------------------------------------------------
> At the tone, the time will be 2002-04-11 11:49:27.309181-04
> (1 row)

I have seen this coding practice extremely often and would be very unhappy if
it were not allowed any more. Imho automatic coercions are a good thing
and should be done where possible. Other extensible databases also allow this
without a cast. Imho the main culprit is finding a "number" format that will not
loose precision when implicitly propagated to.

Andreas

Browse pgsql-hackers by date

  From Date Subject
Next Message Zeugswetter Andreas SB SD 2002-04-16 18:51:33 Re: Implicit coercions need to be reined in
Previous Message Fernando Nasser 2002-04-16 18:27:17 Re: Operators and schemas