Well if you define it as no powerful feature I'm supposing you are talking about QueryPlanCache. Even if we can, in theory, remove the QueryPlanCache using the old parser we can't remove it using the ANTLR parse; the ANTLR parse is time hungry.
To transform the QueryPlanCache in "per thread QueryPlanCache" and disable it, in web is the same. 2009/9/10 Ayende Rahien <[email protected]> > The problem with the query cache as it stands now is that it is a > threading hazard.It gives stateful objects to multiple threads. > > On Thu, Sep 10, 2009 at 9:48 PM, Fabio Maulo <[email protected]> wrote: > >> 2009/9/10 Ayende Rahien <[email protected]> >> >>> >>> As I see it, we have three options: >>> a/ disable the query cache completely >>> b/ make the query cache a per thread query >>> c/ clone the query from the cache when we give it out >>> >> >> a. When? what you mean ? >> > > Instead of caching things, always create the plan from scratch > > >> remove the query cache mean remove one of the most powerful NH feature >> > > I am not sure that I would call it one of the most powerful features > > >> b. Not viable (if you mean really the query cache) >> >> I agree, it would nullify much of the advantages. > > >> c. please answer to a and b >> > > answered :-) > > >> -- >> Fabio Maulo >> > > -- Fabio Maulo
