But it shouldn't go back to the database to check if it's changed, if it's truly cached. What would be the point of caching, if it had to check anyway?
>> It takes milliseconds for CF to "check" as opposed to many many seconds to retrieve database records that you would normally cache and not HIT the server every time when you know as a developer the result will not often change. My postcode example in point, say 10,000+ records? That is when you use caching. -- You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to cfaussie@googlegroups.com. To unsubscribe from this group, send email to cfaussie+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en.
