Re: array support patch phase 1 patch - Mailing list pgsql-patches

From Joe Conway
Subject Re: array support patch phase 1 patch
Date
Msg-id 3EDA95CD.5080404@joeconway.com
Whole thread Raw
In response to Re: array support patch phase 1 patch  (Joe Conway <mail@joeconway.com>)
Responses Re: array support patch phase 1 patch
List pgsql-patches
Joe Conway wrote:
> Next question this begs is, should I work on a '<' operator for arrays?
> And if so, how is the behavior defined? Hannu suggested
> element-by-element, analogous to character-by-character text string
> comparison. Comments?

I created an equality operator for aclitem, and then all was well until
I finished the above (i.e. I created array-array operators for "<>",
"<", ">", "<=", and ">=" based on the text comparison analogy). Now on
ANALYZE (and therefore on initdb) I get this:

template1=# analyze;
ERROR:  Unable to identify an ordering operator for type aclitem
         Use an explicit ordering operator or modify the query

This is where I ran into the problem with an equality operator earlier.
Problem this time is that an ordering operator makes no sense for
aclitems -- does it? Any thoughts on how to work around this?

Joe


pgsql-patches by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: PGSQL transla
Next
From: greg@turnstep.com
Date:
Subject: Re: Valid HTML/XHTML output for psql