Re: array support patch phase 1 patch

From: Joe Conway <mail(at)joeconway(dot)com>
To:
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Patches (PostgreSQL)" <pgsql-patches(at)postgresql(dot)org>
Subject: Re: array support patch phase 1 patch
Date: 2003-06-02 00:09:49
Message-ID: 3EDA95CD.5080404@joeconway.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message greg 2003-06-02 00:43:28 Re: Valid HTML/XHTML output for psql
Previous Message Alvaro Herrera 2003-06-02 00:03:15 Re: PGSQL transla