Of course, storing a reference as to the existance of a file in a database has inherent dangers, even worse if the queries are cached.
----- Original Message ----- From: "Lucas Sherwood" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, October 19, 2002 12:40 PM Subject: RE: [ cf-dev ] FileExists performance > Main thing to remember here is that the database results can be cached either by the database or by CF (using query caching) so on heaver load, the DB solution is prefered... > > L. > > -----Original Message----- > From: Taz -=TT=- [mailto:chris@;cfmaster.co.uk] > Sent: 18 October 2002 17:58 > To: [EMAIL PROTECTED] > Subject: Re: [ cf-dev ] FileExists performance > > > Not sure about that one. > > The best way to find out is to compare the two. You could loop through 100 times with a GetTickCount to get a decent comparison > > Taz > > > > Is there a signficant performance gain by storing whether or not an > > image > exists in a database rather than using FileExists? > > > -- > ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ > > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] For human help, e-mail: [EMAIL PROTECTED] > > -- > ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ > > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > For human help, e-mail: [EMAIL PROTECTED] > > -- ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] For human help, e-mail: [EMAIL PROTECTED]
