| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Does anybody use ORDER BY x USING y? |
| Date: | 2005-09-18 20:19:06 |
| Message-ID: | 432DCBBA.1070201@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Martijn van Oosterhout wrote:
>On Sun, Sep 18, 2005 at 12:34:10PM -0700, Josh Berkus wrote:
>
>
>>>All we lose is the ability to say USING [arbitrary op]. Does anybody
>>>use this. Would people object to requiring the operator after USING to
>>>be part of an operator class?
>>>
>>>
>>Hmmm ... would this prevent the hackish workaround for case-insensitive sort?
>>
>>
>
>Err, which hackish workaround would that be? The right solution is
>citext which creates it's own operator class. This doesn't have
>anything to do with functional indexes either.
>
>
Last time I looked it appeared to have significant limitations, and some
considerable inefficiencies (e.g, copying the strings and folding them
to canonical case on every comparison). I would certainly be extremely
wary of just saying "that's the solution".
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Hansen | 2005-09-18 20:26:10 | Re: Does anybody use ORDER BY x USING y? |
| Previous Message | Martijn van Oosterhout | 2005-09-18 20:01:22 | Re: Does anybody use ORDER BY x USING y? |