SEO

#1 (**permalink**) 04-11-2008, 04:35 AM

I just noticed that these two modules define operator @ as "contains"
and operator ~ as "contained by", which is opposite to the meanings used
by every other datatype.

Is it better to fix this or leave well enough alone?

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend

#2 (**permalink**) 04-11-2008, 04:35 AM

On Sun, 26 Jun 2005, Tom Lane wrote:

> I just noticed that these two modules define operator @ as "contains"
> and operator ~ as "contained by", which is opposite to the meanings used
> by every other datatype.
>
> Is it better to fix this or leave well enough alone?

I'd say for consistencies sake, it should be fixed, but that will break
'backwards compatibility' for anyone using it ...

----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org

#3 (**permalink**) 04-11-2008, 04:35 AM

On Sunday 26 June 2005 21:23, Tom Lane wrote:
> I just noticed that these two modules define operator @ as "contains"
> and operator ~ as "contained by", which is opposite to the meanings used
> by every other datatype.
>
> Is it better to fix this or leave well enough alone?
>

ISTM it will have to be fixed eventually.

--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

#4 (**permalink**) 04-11-2008, 04:35 AM

Robert Treat wrote:
> On Sunday 26 June 2005 21:23, Tom Lane wrote:
> > I just noticed that these two modules define operator @ as "contains"
> > and operator ~ as "contained by", which is opposite to the meanings used
> > by every other datatype.
> >
> > Is it better to fix this or leave well enough alone?
> >
>
> ISTM it will have to be fixed eventually.

We will mention the fix in the release notes if the commit message
mentions it.

--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings

#5 (**permalink**) 04-11-2008, 04:35 AM

On 2005-06-27, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> I just noticed that these two modules define operator @ as "contains"
> and operator ~ as "contained by", which is opposite to the meanings used
> by every other datatype.

These operators are fundamentally confusing because they give no visual
indication as to which operand is the "larger" one.

I'd consider replacing them with something clearer, perhaps @< and @> ?
(i.e. (a @< b) would mean "a is contained by b" and (a @> b) would mean
"a contains b")

--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services

#6 (**permalink**) 04-11-2008, 04:36 AM

Andrew,

> I'd consider replacing them with something clearer, perhaps @< and @> ?
> (i.e. (a @< b) would mean "a is contained by b" and (a @> b) would mean
> "a contains b")

Ltree uses those operators in that way, I believe.

--
Josh Berkus
Aglio Database Solutions
San Francisco

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

Sigh, another contrib/cube and contrib/seg problem