On Thu, Jul 31, 2014 at 10:03:00AM -0400, Tom Lane wrote:
2. text is the preferred type among the string class, so any case where
you have text on one side and some other string type on the other is
going to get resolved as text vs text.
Because of #1, domain-specific functions and operators
On Thursday, July 31, 2014, Adam Mackler-5 [via PostgreSQL]
ml-node+s1045698n5813494...@n5.nabble.com
javascript:_e(%7B%7D,'cvml','ml-node%2bs1045698n5813494...@n5.nabble.com');
wrote:
On Thu, Jul 31, 2014 at 10:03:00AM -0400, Tom Lane wrote:
2. text is the preferred type among the string
Adam Mackler pgsql-gene...@mackler.org writes:
One final question: the 'CREATE CAST' command got my interest. I'm
assuming that when the docs say it 'performs a conversion between two
data types,' that the meaning of data type includes only those
created using 'CREATE TYPE' and excludes
Adam Mackler-5 wrote
(Cross-posted to StackOverflow:
http://stackoverflow.com/questions/25041100/postgresql-user-defined-operator-function-what-parameter-type-to-use-for-uncast
)
I'm defining my own domain and a equality operator.
Next I create an equality operator to do case-insensitive
On Wed, Jul 30, 2014 at 10:59:28PM -0700, David G Johnston wrote:
ISTM that if this was supported you would be doing it correctly.
Thank you for the quick response. I'm not understanding you. Could you
elaborate?
The main problem is you are abusing DOMAIN - which is strictly the
base
On Thu, Jul 31, 2014 at 12:19 AM, Adam Mackler-5 [via PostgreSQL]
ml-node+s1045698n5813399...@n5.nabble.com wrote:
On Wed, Jul 30, 2014 at 10:59:28PM -0700, David G Johnston wrote:
ISTM that if this was supported you would be doing it correctly.
Thank you for the quick response. I'm not
David G Johnston david.g.johns...@gmail.com writes:
On Thu, Jul 31, 2014 at 12:19 AM, Adam Mackler-5 [via PostgreSQL]
ml-node+s1045698n5813399...@n5.nabble.com wrote:
Can you explain what the abuse is? Also why the = operator does not
work even without the domain?
When you write,
