Hello, Thanks for the suggestions.
The cache is designed to be cross session. a use A can retrieve the cached result of the same query executed by a user B. I don't know if setting session variables will make any sense. ~DeD 2010/8/5 Brian Moon <[email protected]> > On 8/5/10 2:13 PM, Tim Soderstrom wrote: > >> Well, that's my point about per-session. You can just enable the >> cache as part of your connection setup sequence and call it done. >> > > I think that is not very DBA friendly. A DBA may not have access to the > code and even if they could, getting changes pushed through in code in some > places can be a nightmare. > > I think the the option to have it default ON with the ENABLE/DISABLE > commands gives everyone the most power. > > > -- > > Brian. > -------- > http://brian.moonspot.net/ > > _______________________________________________ > Mailing list: https://launchpad.net/~drizzle-discuss > Post to : [email protected] > Unsubscribe : https://launchpad.net/~drizzle-discuss > More help : https://help.launchpad.net/ListHelp >
_______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
