Hi,
Giles Lean:
> > So, the rule we thought we had for generating index bounds falls flat,
> > and we're back to the same old question: given a proposed prefix string,
> > how can we generate bounds that are certain to be considered <= and >=
> > all strings starting with that prefix?
>
> To confess ignorance, why does PostgreSQL need to generate such
> bounds?
To find the position in the index where it should start scanning.
> Then there are wide characters, including some encodings that are
> stateful.
Personally, I am in the "store everything on the server in Unicode"
camp. Let the parser convert everything to Unicode on the way in,
and vice versa.
There's no sense, IMHO, in burdening the SQL core with multiple
character encoding schemes.
--
Matthias Urlichs | noris network GmbH | [EMAIL PROTECTED] | ICQ: 20193661
The quote was selected randomly. Really. | http://smurf.noris.de/
--
I loathe that low vice curiosity.
-- Lord Byron
