Hi, > What does the the etc. etc. refer to?
For example session settings. But concurrency is also a problem. I think a session cache is OK; I don't think a per-user cache is worth the effort. Regards, Thomas On Thu, Nov 7, 2013 at 5:37 PM, Rami Ojares <[email protected]> wrote: > > Can't do that, because of differences in access rights, etc, etc. > between sessions > > What does the the etc. etc. refer to? > Namely if the problem was only the access rights then instead of session > cache we could have user cache. > > - Rami > > 7.11.2013 10:04, Noel Grandin kirjoitti: > > >> >> 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. > -- 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.
