Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrectly displaying data on table's charset vs column collation charset #3612

Open
salvor-hardin opened this issue Dec 10, 2019 · 0 comments
Open

Comments

@salvor-hardin
Copy link

@salvor-hardin salvor-hardin commented Dec 10, 2019

  • Sequel Pro Version: Nightly 5446 (97c1b85)
  • macOS Version: 10.14.6
  • MySQL Version: 5.7.28

Description
Data displayed on a table should be using character set by collation of the column, not by the table charset.

Steps To Reproduce
CREATE TABLE t_utf8_utf8 (
value varchar(128) NOT NULL DEFAULT ''
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

INSERT INTO t_utf8_utf8 (value)
VALUES
('Apple iPhone アクセサリ');

t_utf8_utf8

CREATE TABLE t_utf8_latin (
value varchar(128) CHARACTER SET utf8 NOT NULL DEFAULT ''
) ENGINE=MyISAM DEFAULT CHARSET=latin1;

INSERT INTO t_utf8_latin (value)
VALUES
('Apple iPhone アクセサリ');

t_utf8_latin

You should see the same on both tables, as the table or the column is defined as uft8, however the client prints ??? for the Japanese characters (probably using the table charset for all the contents vs the COLLATED charset) when utf8 is the collation of the column but latin1 the charset of the table.

Expected Behaviour
I expect to see the same info on both tables.

Additional Context

Including screenshots.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.