mikeae21
commented
7 years ago I also found that it would be easier to store a fie path to an image and storing that on the database for several reason mainly it being difficult to store and actual image to a database also because it would use a lot of space which will in turn be extremely expensive.
another alternative i thought of was since we are simply making a color palette, we can store the individual red green blue (RGB) values of the color into the database and load them back to a user of the application so they can take there palette with them anywhere they go. I personally think that would be the best way to go using a simple SQL database that can be imported and exported through either a local database(If there's not an internet connection), or a shared one.
http://stackoverflow.com/questions/785551/how-could-i-store-a-color-in-a-database-field http://stackoverflow.com/questions/3748/storing-images-in-db-yea-or-nay
The research I did on the database for images varies based on what our app will do with it. Most of the websites suggest using DB2. “It supports a variety of image formats like GIF, JPEG, BMP, and TIFF, creates and stores a thumbnail of the image. It is also used to retrieve a thumbnail or a full-size image, searches the images based on data that you maintain, such as a name, number, or description. It can also search by data that the DB2 Image Extender maintains, such as a name, number, or description. It can also search by data that the DB2 Image Extender maintains, such as the format of the image or its distribution of colors, etc.”. Another option would be to store the pictures on the file system and picture locations in the database.
http://web.simmons.edu/~weigle/DIGCOLL/Image%20Database.pdf https://github.com/oracle/docker-images http://stackoverflow.com/questions/561447/store-pictures-as-files-or-in-the-database-for-a-web-app https://www.upwork.com/hiring/data/a-guide-to-database-technology/