Hey all, Similar to the charsets conversation, we were also talking about collations. Currently, of course, we do these per-column, with defaults available per table and per schema. How useful is this really? What are people doing who are supporting multi-languages in their systems. Are they _actually_ storing the multi-language data in different columns with different collations?
On the other hand, if there was a per-server collation set by locale, would that be sufficient? I'm asking for two reasons. One, targeting the cloud rather than the enterprise, I'm wondering how many people are wanting their database to handle multi-language sorting directly. The second is that in the quest to remove our internally implemented charset/collation situation, the other libs that do this don't seem to have a good way to do per-method collation picking. So if we don't actually need to have the collation switch during the lifetime of the process, we can use system locale processing. If we _do_ there are other, less attractive options... although we'll do what we have to do I suppose. Monty _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
