Re: dlgOperator_patch - Mailing list pgadmin-hackers

From Dave Page
Subject Re: dlgOperator_patch
Date
Msg-id 03AF4E498C591348A42FC93DEA9661B844B5D4@mail.vale-housing.co.uk
Whole thread Raw
In response to dlgOperator_patch  ("Hiroshi Saito" <saito@inetrt.skcapi.co.jp>)
List pgadmin-hackers

> -----Original Message-----
> From: Hiroshi Saito [mailto:saito@inetrt.skcapi.co.jp]
> Sent: 10 September 2003 03:24
> To: Dave Page
> Cc: pgadmin-hackers@postgresql.org
> Subject: Re: [pgadmin-hackers] dlgOperator_patch
>
>
> > This is one that is not in pga2 - any ideas?
>
> MERGES is specified tacitly.
> Default name in the preparation is put.
> I don't think that it is a problem that it doesn't have
> chkbox.

I think it has as much right to be there as HASHES, however whilst there
is a oprcanhash column in pg_operator, there is no oprcanmerge column.
So what defines a mergeable operator?

> However, are LTCMP, GTCMP necessary?

Yes, I think so. You can specify them when you create an operator (they
are shown as < operator and > operator btw.).

Regards, Dave.

pgadmin-hackers by date:

Previous
From: "Dave Page"
Date:
Subject: Re: pgadmin3.chm in CVS
Next
From: Jean-Michel POURE
Date:
Subject: ./configure patch needed to build portable SRPMs