img src base64 mysql_存储在数据库中的图像直接或为Base64的数据?

bd96500e110b49cbb3cd949968f18be7.png

The common method to store images in database is to convert image to base64 data then storing. This process will increase the size 33%. Alternatively it is possible to directly store image BLOB; for example:

$image = new Imagick("image.jpg");

$data = $image->getImageBlob();

$data = $mysqli->real_escape_string($data);

$mysqli->query("INSERT INTO images (data) VALUES ('$data')");

and display the image with

By the latter method, we save 1/3 storage space. Why storing base64 data into database is the common method for storing images in database?

UPDATE: There are many debates about advantages and disadvantages of storing images in databases, and most people believe it is not a practical approach. Anyway, here I assume we store image in database, and discussing the best method to do so.

解决方案

Pro base64: the encoded representation you handle is a pretty safe string. It contains neither control chars nor quotes. The latter point helps against SQL injection attempts. I wouldn't expect any problem to just add the value to a "hand coded" SQL query string.

Pro BLOB: the database manager software knows what type of data it has to expect. It can optimize for that. If you'd store base64 in a TEXT field it might try to build some index or other data structure for it, which would be really nice and useful for "real" text data but pointless and a waste of time and space for image data. And it is the smaller, as in number of bytes, representation.

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值