> > Do you have an need to worry about current data? Because if you hold
that
> > large data set too long how long is it before it becomes outdated and
> > invalid? or does it stay static?
>
> Simple answer: If that's true for your app, don't use this feature. OR...
> every time you update the info in the DB, update your query object in RAM
> too.
>
> Here's another example of how it could be helpful:
>
> Allaire's Support Forums, everyone's used this right? What if the search
> results were stored in a query object which you could re-order by date,
> author, subject, at will without making a round trip to the DB. You could
> also do the "Get next 10 records" without going back to the db. Depending
> on how much ram you have on your machine and how many users are on it, you
> could probably browse the full message bodies without a round trip too.
>
> -Cameron
Do we even know if this feature will allow you to query persistant queries
(can it use a cached query?) or only queries from the current request? In
CF currently, the query is in memory anyway, so adding the ability to run a
query against it shouldn't really exact addtional memory requirements.
Sounds like it could be an enormous memory hog if used as above.
Jim
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
