Re: incorrect char() string for bigint column
Posted by:
Rick James
Date: August 07, 2011 11:31PM
1. Use SHOW CREATE TABLE so we can see the CHARSET and COLLATION being used.
2. For such purposes, use BINARY, not CHAR.
3. HEX() is another possibility.
4. Probably the 81 was not recognized as valid utf8 and turned into the "replacement character", hex EFBFBD:
http://www.fileformat.info/info/unicode/char/fffd/index.htm
5. Maybe use BINARY(8) instead of BIGINT? Each takes exactly 8 bytes.
Subject
Views
Written By
Posted
1582
August 07, 2011 06:58PM
840
August 07, 2011 07:36PM
995
August 07, 2011 10:09PM
799
August 07, 2011 10:21PM
Re: incorrect char() string for bigint column
863
August 07, 2011 11:31PM
962
August 07, 2011 11:52PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.