>>Images/Documents are comprised of data. I knew some one will point this out. An image is "data" for the eye, nothing a "database" can see and will care of ;-) An employee is data: you can retreive them by name, age, salary, whatever. The only data in an image are just pixels, which no database is aware of and no user is interested in anyway, except for retreiving as a whole. Picture editors deal with pixels, not databases.
When databases will be able to sort images by average hue or lightness, I'll say images should be stored in the database, when one will be able to query a database to get all "images higher than 1000 pixels", then I'll say images should be stored in the database. As far as I know, no database will do that. -- _______________________________________ REUSE CODE! Use custom tags; See http://www.contentbox.com/claude/customtags/tagstore.cfm (Please send any spam to this address: [EMAIL PROTECTED]) Thanks. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:224942 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
