Timeline for What is the performance impact of using CHAR vs VARCHAR on a fixed-size field?
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 16, 2018 at 15:33 | history | edited | Jack Douglas | CC BY-SA 4.0 |
added example of storing in binary with input from Rick's comment
|
| Aug 16, 2018 at 5:11 | comment | added | Rick James |
Changing to BINARY does very little unless you also use UNHEX(). That is, you can store UNHEX(MD5(x)) into a 16-byte BINARY(16) to save significant space over storing MD5(x) into CHAR(32) CHARACTER SET ascii.
|
|
| May 23, 2017 at 12:40 | history | edited | CommunityBot |
replaced http://stackoverflow.com/ with https://stackoverflow.com/
|
|
| May 25, 2011 at 12:28 | history | edited | Jack Douglas | CC BY-SA 3.0 |
added 238 characters in body
|
| May 25, 2011 at 12:25 | comment | added | Jack Douglas | MD5 can be 32 byte hex or 16 byte (128 bit) binary. Thanks for the useful info about charset - I'll update my answer | |
| May 25, 2011 at 12:05 | comment | added | ovais.tariq | for a char(32) column with a character set of utf-8, every value would need 32x3 bytes for storage. Why would you need to set the MD5 hash value to be utf-8. Converting to binary(32) would need 32 bytes per value. | |
| May 17, 2011 at 18:53 | comment | added | Jack Douglas |
@Jason - encoding doesn't apply to binary - or have I misunderstood?
|
|
| May 17, 2011 at 17:36 | comment | added | Jason Baker | I'm planning on converting this into a binary. Now that I think about it though, the size shouldn't be any different just based on whether I'm using a byte or a char since our encoding is utf-8. Or am I wrong? | |
| May 10, 2011 at 21:17 | comment | added | RThomas | Good call on changing to binary. | |
| May 10, 2011 at 21:15 | history | answered | Jack Douglas | CC BY-SA 3.0 |