Unfortunately there's no caching for TQL queries at all, you need to roll your own. Look at query.getParameters() and query.getTQL() to generate a unique key.
It should be noted that there's no cache for readByPropertyMap() either, Transfer will always hit the database to determine which key to fetch from the cache. On Nov 25, 2:48 pm, NickHaggmark <[email protected]> wrote: > Out of curiousity, how does it make cache determinations using the TQL > route? Does it recognize class elements in the TQL and cache using > cfquery caching using durations based on your class cache > configurations or does it cache on fixed timeline? Does that make > sense? > > Thx. > > Nick > > On Nov 25, 2:33 pm, Mark Mandel <[email protected]> wrote: > > > > > Yeah, go the TQL route.. I don't think there is a way to specify a null in a > > property map. -- Before posting questions to the group please read: http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer You received this message because you are subscribed to the Google Groups "transfer-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/transfer-dev?hl=en
