--=====================_42872252==_.ALT
Content-Type: text/plain; charset="us-ascii"

:-) I've already decided I can't use it because of the (alleged) 100 query limit. This 
:site will have to potentially scale larger than that, so I am going to use session 
:variables for queries, ie:

        lock session
        cfquery name=session.mysearch
        ...SQL...
        /cfquery
        unlock session

        and

        lock readonly session
        cfoutput query=session.mysearch
        ...do stuff with query...
        /cfoutput
        unlock session

If everyone thinks that locking session around the cfoutput will impact performance 
too much, I can move it to a variable first:

        lock readonly session
        variable.mysearch = session.mysearch
        unlock session
        cfoutput query=variable.mysearch
        ...take your time doing stuff with query...
        /cfoutput


At 09:40 PM 8/4/00 -0400, Dave Watts wrote:
>> So my cached queries are safe to use. Each user will have his
>> own cached query, even though they are not attached to a
>> "session" scope in any way. Except when two users issue the
>> exact same set of criteria in which case, in an even better
>> win, they share a cached query since their results will be
>> the same anyway.
>
>This is true, but if it's likely that a cached query won't be reused, you
>probably don't want to cache it.
>
>Dave Watts, CTO, Fig Leaf Software
>http://www.figleaf.com/
>voice: (202) 797-5496
>fax: (202) 797-5444


---------------------------------------------------------------------------
Peter Theobald, Chief Technology Officer
LiquidStreaming http://www.liquidstreaming.com
[EMAIL PROTECTED]
Phone 1.212.545.1232 Fax 1.212.679.8032

--=====================_42872252==_.ALT
Content-Type: text/html; charset="us-ascii"

<html>
<font size=3>:-) I've already decided I can't use it because of the
(alleged) 100 query limit. This site will have to potentially scale
larger than that, so I am going to use session variables for queries,
ie:<br>
<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>lock
session<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>cfquery
name=session.mysearch<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>...SQL...<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>/cfquery<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>unlock
session<br>
<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>and<br>
<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>lock
readonly session<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>cfoutput
query=session.mysearch<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>...do
stuff with query...<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>/cfoutput<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>unlock
session<br>
<br>
If everyone thinks that locking session around the cfoutput will impact
performance too much, I can move it to a variable first:<br>
<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>lock
readonly session<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>variable.mysearch
= session.mysearch<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>unlock
session<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>cfoutput
query=variable.mysearch<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>...take
your time doing stuff with query...<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>/cfoutput<br>
<br>
<br>
At 09:40 PM 8/4/00 -0400, Dave Watts wrote:<br>
<blockquote type=cite cite>&gt; So my cached queries are safe to use.
Each user will have his<br>
&gt; own cached query, even though they are not attached to a<br>
&gt; &quot;session&quot; scope in any way. Except when two users issue
the<br>
&gt; exact same set of criteria in which case, in an even better<br>
&gt; win, they share a cached query since their results will be<br>
&gt; the same anyway.<br>
<br>
This is true, but if it's likely that a cached query won't be reused,
you<br>
probably don't want to cache it.<br>
<br>
Dave Watts, CTO, Fig Leaf Software<br>
<a href="http://www.figleaf.com/" eudora="autourl">http://www.figleaf.com/</a><br>
voice: (202) 797-5496<br>
fax: (202) 797-5444</font></blockquote><br>

<font size=2><b><br>
---------------------------------------------------------------------------<br>
Peter Theobald, </b>Chief Technology Officer<br>
</font><font size=3 color="#0000FF"><b>LiquidStreaming
</b></font><a href="http://www.liquidstreaming.com/" eudora="autourl"><font size=2 
color="#0000FF"><u>http://www.liquidstreaming.com</a><br>
</u></font><font size=2>[EMAIL PROTECTED]<br>
<b>Phone</b> 1.212.545.1232 <b>Fax</b> 1.212.679.8032<br>
</font></html>

--=====================_42872252==_.ALT--

------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/[email protected]/
To Unsubscribe visit 
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a 
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.

Reply via email to