3 ms·
Point 1 is silly - this depends greatly on what your application needs to do. If you need to store the image together with the metadata or other information rel
by hipjim 10y ago
Point 1 is silly - this depends greatly on what your application needs to do. If you need to store the image together with the metadata or other information related to the image that is transactional data - then storing the image in the database is the way to go. This also helps a lot with database backups, migrations etc..
- Mister_Snuggles 10y agoYup. Not every PostgreSQL-backed application is a public-facing web app. A fat-client that connects directly to the PostgreSQL database to do "stuff" with transactional data will have a much easier time if any related images are stored alongside the transactional data.