But in the end why would you? if not then it will always be slower to get the images out and the code will be beating on what will no doubt be your most stressed, weakest link ... your database.
Think about how hard you are making to check that an image is correct on your system. You are going to have to write some sort of utility just to look at the images stored. Your database could start having issues with trying to manage such large data items. Do you need the ACID properties of a database? If you, really, really do a hybrid approach that has some value is using a database like apache's derby to store your images. (in other words not your main database) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
