Storing SMALL images in MySql database and why is it different for SQL Server?

I understand that the question of storing images in a MySql database has been asked many times before, but I haven't seen anything said about really small images (~1-10KB) or rather it's always generalized to images of any size, and that they should always be stored as a location on the file system. The reason I'm asking is because I read here that for Sql Server, using varbinary is more efficient if the images are less than 256KB and for anything above 1MB, it should be stored on the file system. This may be true for Sql Server, but is it true for MySql? And if it is true for both, is there an equivalent to varbinary(MAX) since MAX doesn't seem to be an appropriate input for varbinary in MySql(Maybe BLOB, but I hear everyone condemning the use of BLOB for pretty much any reason...).

So to clear it up a bit:

Is it still better, in MySQL, to store images on the file system even if they are very small?

If yes, why is it NOT recommended to do this in SQL Server as stated here (Smaller images are more efficiently stored as varbinary)?

If no, what would be the equivalent to varbinary(MAX) to avoid an error in case my image is slightly above 8K?

I guess I'm really just stuck on the differences between MySQL and SQL Server when in comes to handling images and why recommended practices seem to be different for both.

链接地址: http://www.djcxy.com/p/41870.html

上一篇: 如何制作依赖于其他应用的Android应用？

下一篇: 在MySql数据库中存储小图片，为什么它与SQL Server不同？