Hi Taco,
Well, this *is* a CF list and CF is generally a technology for *web* based applications so you have to expect that kind of slant when you ask about the advantages of storing images in a database. ;)
B)
Taco Fleur wrote:
Hi Brett,
I guess images was a bit of a bad example, even if it was now "not so bad" to store images in the db it certainly would not be a good idea to store images in the db that are used in a websites design and serve them upon each request, my question was more in general (and excluding this scenario).
-- Brett Payne-Rhodes Eaglehawk Computing t: +61 (0)8 9371-0471 f: +61 (0)8 9371-0470 m: +61 (0)414 371 047 e: [EMAIL PROTECTED] w: www.ehc.net.au
--- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
