Hi,
if designing a web application, would it make a differnce if an image field is in a table or the image field is saved in another table with a one-to-one relation.
The assumption is that we won't be doing a "SELECT *"
I've read many similar posts regarding image field, and it seems that the majority don't reccomend storing the image, but storing a link to the image, as the image will affect performance, increase size dramtically, keep record locks longer, etc. Do a keyword search on 'image' in either this forum, or the SQL programming forum, for all related posts.
Be quiet Brain, or I'll stab you with a Q-tip! (Homer Simpson)
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.