On Sun, Sep 18, 2005 at 04:19:06PM -0400, Andrew Dunstan wrote: > >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".
Ok, so citext has its limitations. Case-insensetive sort is hard [1]. My real question was, what was the solution he was referring to using the USING clause? [1] http://lafstern.org/matt/col2_new.pdf -- Martijn van Oosterhout <kleptog@svana.org> http://svana.org/kleptog/ > Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a > tool for doing 5% of the work and then sitting around waiting for someone > else to do the other 95% so you can sue them.
pgp8mAO26x7IC.pgp
Description: PGP signature
