在存储Ethereum API获取的地址数据时，原始的varchar列被使用。考虑到数据一致性，文章讨论了使用varbinary和BINARY数据类型的优缺点。varbinary可以节省空间并防止非十六进制数据的存储，但需要转换。BINARY(20)提供数据校验，但显示为十六进制时需额外处理。建议采用BINARY结合创建hexa视图以兼顾存储和查看需求。
I'm using the Ethereum api. I want to store the information from the api into a mysql table.
The address data looks like:
0x3f5ce5fbfe3e9af3971dd833d26ba9b5c936f0be
0x1d80982502f3bb75654df13aa32bbd5ac9cab7d6
0xaf13bbdbe1ff53c2df7109a53c217320d2d76ee2
...
I've been using just varchar column for these characters. Are there a better data type? I'm thinking maybe varbinary but I don't know if there's any advantages. The disadvantage is that the sql code will be messier as I will have to HEX() and UNHEX().
解决方案
For me no specific type exists, you need to choose between text and binary :
pros : simplicity
cons : you need more space disk (~+100%)
cons : you risk to store invalid non hexa data
BINARY(20) :
pros : reduce space disk
pros : you can't store invalid d
最低0.47元/天 解锁文章
扫一扫
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
