Im not sure it's the same problem. The queries mentioned in the description of bug #6128 are not using table-aliases (e.g. a, b and c), like in my sample query. These kind of queries are generated by the ClusterBuilder, therefore I expected the multilevel cache to cache them.
At least we agree it is a bug. Rob van Maris Technical Consultant Quantiq xmedia & communication solutions Koninginneweg 11-13 1217 KP Hilversum T +31 (0)356257211 M +31 (0)651444006 E [EMAIL PROTECTED] > Rob van Maris <[EMAIL PROTECTED]> wrote: > > Our logfiles indicate that the relatednodes tag generates > queries like > > this: > > > > select c.otype, c.number, a.number > > from v15_aankeilers a, v15_insrel b, v15_images c > > where a.number=2561 AND a.number=b.snumber AND c.number=b.dnumber > > > > Contrary to what I would expect, it seems the result of > these queries > > are not cached, so each subsequent use of the relatednodes > tag results > > in another query. > > > > Is this a bug? I for one would expect these queries to go into the > > multilevel cache. What is the situation in 1.7 (our tests > were using > > 1.6.3). And where does the RelatedCache fit in? > > That might be a bug #6128, which is fixed in 1.7. > > Michiel > > > -- > Michiel Meeuwissen > Mediapark C101 Hilversum > +31 (0)35 6772979 > nl_NL eo_XX en_US > mihxil' > [] () >
