Why not jus use QoQ on the cached queries, rather than converting them?
May not be QUITE as fast... but?
a typical usage is processing a couple of hundred elements in an array
of structs..."if this then insert else update" sort of thing.
for each array loop iteration there's abot 6-10 lookups and decisions
to be done.
for the couple of hundred inserts and updates to process and then
redrawing the datagrid at the end (did I mention that it *should* be a
flex app with remoting... but isn't?) every bit helps. Previously,
other parts of the system just re-re-re-queried away happily.. some
with cachewithin, some with none.
yes, I can move the whole lot down to the database but the amount of
decisons, formatting and error trapping to do, it just ain't worth it.
CF is the best place to process this lot.
> The other option is - cache both the query, and the struct version...
and lookup depending on what you need.
That means you would have to roll your own caching system such that
when the query gets refreshed, your struct does too.
yeah, option one. I just have to guess when the data gets dirty to
re-run the caching...
cheers
b
You are subscribed to cfcdev. To unsubscribe, please follow the instructions at
http://www.cfczone.org/listserv.cfm
CFCDev is supported by:
Katapult Media, Inc.
We are cool code geeks looking for fun projects to rock!
www.katapultmedia.com
An archive of the CFCDev list is available at
www.mail-archive.com/[email protected]
