| From: | David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Would you help to review our modifications |
| Date: | 2014-10-20 16:02:32 |
| Message-ID: | 1413820952474-5823679.post@n5.nabble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
rohtodeveloper wrote
> So how to deal with this kind of situation if I want a implicit
> conversion?
As of the out-of-support 8.3 release many of the implicit casts previously
defined have been changed to explicit casts. It is a catalog change -
obviously, since you can still define implicit casts - so if you absolutely
must have the pre-existing cast be implicit you can modify the catalog
directly.
You may wish to describe why you think this is the solution you need - with
implicit casting there are generally more downsides that upsides.
Dave
--
View this message in context: http://postgresql.1045698.n5.nabble.com/Would-you-help-to-review-our-modifications-tp5823666p5823679.html
Sent from the PostgreSQL - hackers mailing list archive at Nabble.com.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2014-10-20 16:16:52 | Re: Trailing comma support in SELECT statements |
| Previous Message | David E. Wheeler | 2014-10-20 15:59:53 | Re: Trailing comma support in SELECT statements |