Timeline for best column type for hashed data in mysql
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 3, 2019 at 4:15 | answer | added | Rick James | timeline score: 5 | |
| Jan 2, 2019 at 14:06 | comment | added | Kondybas |
Double transform bin --> hex --> b64 is just a waste of resources. Use the fixed-size BINARY(32) column for storing the data. It has no collation so no overhead for processing and also it is indexed way better that collated charsets.
|
|
| Jan 2, 2019 at 13:00 | answer | added | Jonathan Fite | timeline score: 1 | |
| Jan 2, 2019 at 11:05 | review | First posts | |||
| Jan 2, 2019 at 12:02 | |||||
| Jan 2, 2019 at 11:01 | history | asked | masciugo | CC BY-SA 4.0 |