Image data is stored in the database as a blob, it's not a major issue for low rate applications but can be if you for example run this on a Raspberry Pi with a smaller SD card. Once the disc fills there can be performance issues related to copying and deleting the data. Some databases have image types that might be supported, or this could be done instead by writing files to disc and storing the reference. The reason that wasn't done initially was concerns over someone deleting a file and breaking a reference, but that seems like a corner case that isn't worth supporting.
Image data is stored in the database as a blob, it's not a major issue for low rate applications but can be if you for example run this on a Raspberry Pi with a smaller SD card. Once the disc fills there can be performance issues related to copying and deleting the data. Some databases have image types that might be supported, or this could be done instead by writing files to disc and storing the reference. The reason that wasn't done initially was concerns over someone deleting a file and breaking a reference, but that seems like a corner case that isn't worth supporting.