Jim Winstead wrote: > On Tue, Sep 30, 2008 at 3:14 PM, Monty Taylor <[EMAIL PROTECTED]> wrote: >> So rather than build our own system of dealing with all of this - I'd >> love to see us be able to use some of what's already there. Better than >> the C version of this, the C++ one seems to understand you might want to >> use more than just one global locale. Now, I'm not sure how charsets >> enter in to this setup... but the ability is there to deal with >> collations, numbers, currency and dates. Any thoughts? > > just the same one i always bring up -- what happens to your indexes > when the system collation changes? i don't mean switching to a > different collation, i mean when you upgrade your system and the > zh_CN.UTF8 locale suddenly sorts two characters a different way.
It's an interesting question... I think the easy answer is that no one should upgrade their systems. :) It seems like there isn't a good way for Drizzle to know that directly. If your query was trusting index sort order, then you could get different results from that compared with the results from a filesort... and if subsequent inserts into the index were done with the new collation info you could get very odd results inside of the index, which you would have to solve by asking the system to rebuild its indexes. I wonder how often this comes up, and if it's worth the cost of putting in some sort of collation sanity check every so often... or if that should just be a user admin task? > the code does look pretty straightforward and otherwise reasonable. Good... thanks. 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
