Quote
How about the performance if I store LARGEBLOB?
It's not so much the performance of any data type that's the issue here.
It's the whole process of taking the image, storing it into the database and then, whenever the image is needed, retrieving the image data, writing it to a disk file and then sending [the URI of] that file to the client's browser in order for it to be displayed.
All this, instead of leaving the image in a disk file
all the time and only holding a note of
where that file is in the database.
* Zero overhead putting the image into the database.
* Zero overhead in getting the image out of the database, because it's already sitting in a file, where it needs to be. [/list]
Hence, better performance.
Quote
Is there a datatype to store just the path of the image just like Oracle's BFILE or I have to do it manually in my code?
varchar will do perfectly well.
Regards, Phill W.