Just had an interesting issue with an encoding mess on a column containing non-ASCII (Russian) text. The solution …(CONVERT(CONVERT(column USING binary) USING utf8) USING cp1251) WHERE id=123; This can be further simplified. After 2nd conversion the… binary) USING utf8) WHERE id=123; The same trick could be applied to fix notorious KOI8-R vs CP1251 encoding issues in…
Post: PHP vs. BIGINT vs. float conversion caveat
January 10, 2008 By 27 Comments
… not enough and you have to use BIGINT 64-bit ids; e.g. if you are encoding additional information like the server ID into high bits of the ID. I had already written about the mess that 64-bit integers… numeric value handling: it can be used to workaround signed vs. unsigned int issues; it helps with float formatting; always a…
Comment: PHP vs. BIGINT vs. float conversion caveat
January 11, 2008 By 27 Comments
…MySQL Performance Blog wrote an interesting post today on PHP vs. BIGINT vs. float conversion caveatHere’s a quick excerpt Sometimes you… not enough and you have to use BIGINT 64-bit ids; e.g. if you are encoding additional information like the server ID into high bits of the ID. I had already written about the mess that 64-bit integers…
