On Wed, Jul 02, 2008 at 07:22:10PM +0100, Gregory Stark wrote: > > Because the SQL spec says so. Also, if we don't put them in schemas, > > we have no nice way to distinguish built-in and user-defined collations, > > which creates a problem for pg_dump. > > Out of curiosity, what is a "user-defined collation"? Are there SQL statements > to go around declaring what order code points should be sorted in? That seems > like it would be... quite tedious!
Not that we'll ever use it, but ICU for example allows users to say: "use collation X but move this code point somewhere else", essentially allowing users tweak the collation on a small scale. In any case, whatever collation library is used, we're unlikely to predefine every possible collation in the system, there's too many (assuming they're denumerable). Have a niceday, -- Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/ > Please line up in a tree and maintain the heap invariant while > boarding. Thank you for flying nlogn airlines.
signature.asc
Description: Digital signature
