On 01/13/2013 08:06 PM, Dimitri Fontaine wrote:
> Hannu Krosing <hannu(at)2ndQuadrant(dot)com> writes:
>>> Does this hint that postgreSQL also needs an sameness operator
>>> ( "is" or "===" in same languages).
>> How do people feel about adding a real sameness operator ?
> Well. I would prefer it if we can bypass the need for it.
What is actually sufficient for current problem is sameness
which compares outputs of type output functions and also
considers NULLs to be the same.
The reason for not providing equality for xml was not that two xml
files which compare equal as text could be considered unequal in
any sense but that there are some other textual representations
of the same xml which could also be considered to be equal, like
different whitespace between tag and attribute
> Then Do we need the full range of eq, eql, equal and equalp predicates,
> and would all of them allow overriding or just some?
I consider sameness as basic thing as IS NULL, so the sameness
should not be overridable. Extending IS NOT DISTINCT FROM to
do this comparison instead of current '=' seems reasonable.
SELECT '<tag/>'::xml IS DISTINCT FROM '<tag />'::xml
should return TRUE as long as the internal representation of the
two differ and even after you add equality operator to xml
which compares some canonic form of xml and thus would make
SELECT '<tag/>'::xml = '<tag />'::xml ;
In response to
pgsql-hackers by date
|Next:||From: Markus Wanner||Date: 2013-01-14 09:03:48|
|Subject: Re: Re: logical changeset generation v3 - comparison to
Postgres-R change set format|
|Previous:||From: 李海龙||Date: 2013-01-14 07:18:18|
|Subject: Re: I s this a bug of spgist index in a heavy write