Tag Info

New answers tagged

1

Not sure if you found a solution to this but for us it seems to be related to the size of data leaving the VPC. If you run a query with a small result set: show collation like '%utf8_swedish%'; The result returns fine, but if you take away the like and get a large result set back it fails. We're still investigating the problem but not sure you found a ...


0

Try using the utf8_bin collation, e.g. this will show its effect: SELECT _utf8 'Αγάθη' = _utf8 'Αγαθή' COLLATE utf8_bin;


2

Of the several utf8 collations available: mysql> SELECT * FROM information_schema.collations WHERE character_set_name = 'utf8'; +--------------------------+--------------------+-----+------------+-------------+---------+ | COLLATION_NAME | CHARACTER_SET_NAME | ID | IS_DEFAULT | IS_COMPILED | SORTLEN | ...


1

What are the downside of using LC_CTYPE='C' over a specific localization The results of comparisons between strings depends on LC_CTYPE. In practice, the most visible effect is the sort order. 'C' as LC_CTYPE means that the byte order is going to drive comparisons, whereas a real locale means that cultural rules will drive the comparisons. An example ...


1

This is revolves around COLLATION rules (which are part of your locale). Per documentation: The C and POSIX collations both specify "traditional C" behavior, in which only the ASCII letters "A" through "Z" are treated as letters, and sorting is done strictly by character code byte values. Bold emphasis mine. These internal operators: ~<~, ...



Top 50 recent answers are included