Noel, Thanks for the reply. that makes sense with the access rights between sesisons. Liek you mentioned, I was also starting to release that the querry cache is of limited use, and that perhaps (for my case) a cache outside of the database is a better setup anyway. So, I am just now setting the querry cache to 0 and using an external caching mechanism. I assume that setting the query cache to 0 will have no real negative effects, other than simply not caching the result sets of querries a small number of querries. Thanks, -Adam
On Thursday, November 7, 2013 3:04:19 AM UTC-5, Noel Grandin wrote: > > > On 2013-11-04 03:39, Adam McMahon wrote: > > On a similar note, it seems like a global query cache, as opposed to a > separate one for each session, would be useful. > > > > Can't do that, because of differences in access rights, etc, etc. between > sessions. > So we use a page cache, which actually does most of the heavy lifting in > reducing disk access. > The query cache is generally of limited use, which is why it defaults to > being so small. > -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/groups/opt_out.
