You could hash the query string and session id and use that for the variable
name.
SESSION.QUERYCACHE[hash(SESSION.SESSIONID & querystring)] = myquerytocache;
then look in the cache first to see if it exists
if(StructKeyExists(SESSION.QUERYCACHE,hash(SESSION.SESSIONID &
querystring)){ return true; };
On Fri, Feb 26, 2010 at 5:29 PM, Matthew Woodward <[email protected]>wrote:
> Just like you would any other variables--there's nothing special about the
> session scope other than it's unique to each user. Other than that they're
> just variables.
>
> On Feb 26, 2010 2:18 PM, "Jason King" <[email protected]> wrote:
>
> How do I name them then?
>
> Do I still cache the query normally, and stick the cached query's name in
> session scope? Or the entire query in session scope?
>
>
>
>
>
>
> On Fri, Feb 26, 2010 at 4:14 PM, Matthew Woodward <[email protected]>
> wrote:
>
>> >
>> > You can stick more than one query in the session.
>>
>>
>> >>
>> >> On Feb 26, 2010 2:12 PM, "Jason King" <[email protected]> wrote:
>> >>
>> >> Ok, I could do th...
>>
>>
>> >
>> > --
>> > Open BlueDragon Public Mailing List
>>
>> > http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon
>> > mailing list - http://groups.go...
>>
>>
> --
>
> Open BlueDragon Public Mailing List
>
> http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon
> mailing list - http://groups.google...
>
> --
> Open BlueDragon Public Mailing List
> http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon
> mailing list - http://groups.google.com/group/openbd?hl=en
>
> !! save a network - please trim replies before posting !!
>
--
/Kevin Pepperman
--
Open BlueDragon Public Mailing List
http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon
mailing list - http://groups.google.com/group/openbd?hl=en
!! save a network - please trim replies before posting !!
