on 2002/9/10 2:27 PM, "Chris K Chew" <[EMAIL PROTECTED]> wrote:
> We saved images in a db with a previous application, and history is showing > it to be a bad idea. Problems occur when you need to move them to another > db instance and especially another vendor's db. It can also be very slow > for the application to serve them out to browsers all the time. I highly > recommend storing them in the filesystem instead of the db. > > Chris +1 What you can do is store the relative PATH to the image in the db. Then use that to generate the <img> tag to serve the file from the filesystem... Relational databases are a terrible place to store things like images. -jon -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
