Re: Singleton range constructors versus functional coercion notation - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Singleton range constructors versus functional coercion notation
Date
Msg-id 5517.1321984883@sss.pgh.pa.us
Whole thread Raw
In response to Re: Singleton range constructors versus functional coercion notation  (Jeff Davis <pgsql@j-davis.com>)
List pgsql-hackers
Jeff Davis <pgsql@j-davis.com> writes:
> It's a little strange that we allow people to define functions with one
> argument and the same name as a type if such functions are confusing.

As long as your mental model is that such a function is a cast,
everything is fine.  The trouble with the range constructors is that
they aren't really casts, as shown by the fact that when you readtextrange('foo')
you expect 'foo' to be text and not textrange.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: strange nbtree corruption report
Next
From: Pavan Deolasee
Date:
Subject: Re: testing ProcArrayLock patches