On Fri, Sep 08, 2006 at 02:14:58PM +0200, Peter Eisentraut wrote: > So "mathematically", you are right, the collation is a property of the > operation, not of the operands. But semantically, the operands do > carry the information of what collation order they would like to be > compared under, and if two pieces of data with different choices meet, > you need an override.
Sure, but SQL COLLATE handles all that just fine. At no point is the collation a property of the operands. At best is a property of the source of the operands but can be overridden at any point. SQL also covers the case where there is ambiguity, and the writer of the query has to clarify. Collation is hard precisly because it's not a property of the operands, which makes it very difficult to make postgresql do it. > Incidentally, if you buy into that, this would also neatly solve the > problem of how to arrange for column-specific case conversion rules, > which SQL does not address at all. SQL does say that UPPER and LOWER should be handled by Unicode rules, however the notes do mention that they should probably pay attention to the collation and character set, since the results are dependant on them. Have a nice day, -- Martijn van Oosterhout <firstname.lastname@example.org> http://svana.org/kleptog/ > From each according to his ability. To each according to his ability to > litigate.
Description: Digital signature