MySQL proofreading set issues

 Essays and records to facilitate their access to fellow travelers.

#------------------------------------------------I ------------------------------------------- dividing line is a shame

 In the recent review of MySQL, why review it? We should know everything, do not have the skills for a long time have returned to the teacher, because the habit of learning not previously recorded, when the school will not forget,

And when used can not quickly understand, but also to watch the video again or look thick books, so this review essays recorded later for easy viewing.

#------------------------------------------------I ------------------------------------------- dividing line is a shame

Proofreading set issues

Proof set: way of comparison data

Proof set has three formats

_bin: binary, binary comparison, remove the bit, bit by bit comparison is case sensitive

_cs: case sensitive, case sensitive, case sensitive

_ci: case insensitice, case-insensitive, not case sensitive

 

View database supports proof set: Show collation;

 

 

Proof sets Application: only compare data generated when proofreading set to take effect

 

 

Comparison: Use UTF8 the _bin and _ci to verify the effects of different sets of calibration
1. Create a table corresponding to a different set of calibration

 

 

2. Insert Data

- insert data

insert into my_collate_bin VALUES('a'),('A'),('B'),('b');

insert into my_collate_ci VALUES('a'),('A'),('B'),('b');

 

 

3. Comparison: Sort according to a field: the Order by field name [asc | desc]; asc ascending , desc Descending

 

 

Proof set: must be generated in the absence of good data, if they have data, making proof sets Review: So modify invalid

 

Guess you like

Origin www.cnblogs.com/lirongyang/p/11088884.html