might not be caching because your query code is changing with time.

try putting the date functions into T-SQL's version of dateadd():

<cfquery name="qry_getLoggedonUsers" datasource="client_storage"
cachedwithin="#createtimespan(0,0,10,0)#">
        Select  count(cglobal.cfid) as users
        FroM    cglobal,cdata
        Where   lvisit > DATEADD(minute,-20,GETDATE())
        And             cglobal.cfid = cdata.cfid
        And             cdata.app = 'appname'
</cfquery>

> -----Original Message-----
> From: Giles Roadnight [mailto:giles.roadnight@;goldcockerelbooks.co.uk]
> Sent: 07 November 2002 16:26
> To: [EMAIL PROTECTED]
> Subject: RE: [ cf-dev ] Online Users
> 
> 
> Right I have this code:
> 
> <cfquery name="qry_getLoggedonUsers" datasource="client_storage"
> cachedwithin="#createtimespan(0,0,10,0)#">
>       Select  count(cglobal.cfid) as users
>       FroM    cglobal,cdata
>       Where   lvisit > #dateadd("n",-20,now())#
>       And             cglobal.cfid = cdata.cfid
>       And             cdata.app = 'appname'
> </cfquery>
> 
> that works fine but it doesn't cache. Every time it says that 
> it took 10
> ms to run. Not very long but as the table gets bigger this is bound to
> slow down.
> 
> Any reason why? It won't be because it is on the client 
> storage db will
> it?
> 
> 
> Giles Roadnight
> http://giles.roadnight.name
> 
> 
> -----Original Message-----
> From: Spike [mailto:spike@;prisma-it.com] On Behalf Of Spike
> Sent: 06 November 2002 23:21
> To: [EMAIL PROTECTED]
> Subject: RE: [ cf-dev ] Online Users
> 
> What???
> 
> Are you advocating that we should spend say �200 on 1GB of RAM instead
> of getting someone to spend a few days coming up with an slower
> alternative by storing that sort of information in the DB?
> 
> Harumph!
> 
> How's a cowboy programmer supposed to make a living these days?
> 
> ;-)
> 
> Spike
> 
> Stephen Milligan
> Team Macromedia - ColdFusion
> Co-author 'Reality Macromedia ColdFusion MX: Intranets and Content
> Management'
> http://spikefu.blogspot.com
> 
> > -----Original Message-----
> > From: Steve Martin [mailto:steve.martin@;sequence.co.uk] 
> > Sent: 06 November 2002 18:47
> > To: [EMAIL PROTECTED]
> > Subject: RE: [ cf-dev ] Online Users
> > 
> > 
> > By who's criteria?
> > The session scope is there for storing login information of 
> > this nature. Slam in some RAM if you feel that your server 
> > can't cope. 600 users is a pretty teeny weeny small number by 
> > any server's standards.
> > 
> > My usual advice is to avoid trying to come up with esoteric 
> > software engineering solutions to workaround physical 
> > constraints when such constraints can be overcome by spending 
> > 50p on some more memory.
> > 
> > > -----Original Message-----
> > > From: Robertson-Ravo, Neil (REC) 
> > > [mailto:Neil.Robertson-Ravo@;csd.reedexpo.com]
> > > Sent: 06 November 2002 17:12
> > > To: '[EMAIL PROTECTED]'
> > > Subject: RE: [ cf-dev ] Online Users
> > > 
> > > 
> > > well,, after a quick check, the amount of users within the
> > > system could be
> > > 600+ at anyone time.....
> > > 
> > > bit big for the session scope?!
> > > 
> > > 
> > > 
> > > -----Original Message-----
> > > From: Steve Martin [mailto:steve.martin@;sequence.co.uk]
> > > Sent: 06 November 2002 16:44
> > > To: [EMAIL PROTECTED]
> > > Subject: RE: [ cf-dev ] Online Users
> > > 
> > > 
> > > I just store login information in the session scope which
> > > takes care of
> > > flushing itself when the timeout is reached. Why 
> > specifically are you
> > > storing such information in a db? 
> > > 
> > > > -----Original Message-----
> > > > From: Robertson-Ravo, Neil (REC) 
> > > > [mailto:Neil.Robertson-Ravo@;csd.reedexpo.com]
> > > > Sent: 06 November 2002 16:31
> > > > To: '[EMAIL PROTECTED]'
> > > > Subject: [ cf-dev ] Online Users
> > > > 
> > > > 
> > > > This is a no brainer and I must be having a brain fart....
> > > > 
> > > > We have an online table which holds records for each user
> > > > logged onto the
> > > > system after login.  
> > > > These rows have a date logged on etc, and indeed this works 
> > > > well when the
> > > > user signs off as expected (as this removes the rows in 
> question)
> > > > 
> > > > however, what process do you guys have in place when a user
> > > > does NOT sign
> > > > off and simply closes the browser and does not return for 
> > a few days
> > > > later...?
> > > > 
> > > > It means that they remain 'online' in the DB......
> > > > 
> > > > What do you guys have in place... any ideas?
> > > > 
> > > > Neil
> > > > 
> > > > --
> > > > ** 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]
> 
> 
> -- 
> ** 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]


--
** 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]

Reply via email to