haman...@t-online.de writes:
> declaring another operator class helped. At first, however,
> results were sorted deifferent than expected. A little gdb session revealed
> that
> if fact only the FUNCTION 1 entry in the operator class is used
Well, yeah, the function had better match the operators
Hi Tom,
declaring another operator class helped. At first, however,
results were sorted deifferent than expected. A little gdb session revealed that
if fact only the FUNCTION 1 entry in the operator class is used
Regards
Wolfgang Hamann
>>
>> haman...@t-online.de writes:
>> > Now, in versions
haman...@t-online.de writes:
> Now, in versions 8 and later the "using <&-" is rejected,
> the ordering op "needs to be < or > member of a btree operator class".
> What is needed to create the old behaviour again
> - create a complete operator class, including new names for the unchanged
> equal
Hi,
in the old days (version 7.x) I created a set of btree operators
create operator <& (
procedure = mytext_lt,
leftarg = text,
rightarg = text,
commutator = >&,
negator = >=&,
restrict = scalarltsel,
join = scalarltjoinsel
);
etc. for a completeoperator class
create operator cla
