> Is there a reason NOT to put the > images in a database? There are many.
1) You can't manipulate them with file-based tools any more. 2) Handling a request for an image consumes many more resources, since there is now application code and a database involved rather than just a simple static file request. 3) Most databases don't make dealing with BLOBs as simple as MySQL does, so your code becomes rather hard to port. Those are the biggies. Of course there are reasons to do it too, but every time I've put images/templates/files in a database I have lived to regret it. Storing the path seems to work better. - Perrin
