I believe so. On Wed, Mar 18, 2009 at 5:10 PM, Tomek Kott <[email protected]> wrote:
> > using 5.0 > > So does that mean it would be nominally ok to just truncate the table > and let FarCry handle rebuilding the ancestors again? > > On 3/18/09, Blair McKenzie <[email protected]> wrote: > > The ancestor table is used to determine what caches need to be flushed > when > > any given object is changed. > > > > I know that Mat did a lot of fixes to the way the table is used for > > basically the reason you're describing - uncached webskins were being > added > > unnecessarily. Are you using 5.0 or 5.1? If this is a bug I'll pass it on > to > > Matt. > > > > Blair > > > > On Wed, Mar 18, 2009 at 4:39 PM, Tomek Kott <[email protected]> > wrote: > > > >> > >> Hi FC, > >> > >> I either have a bug with dmWebskinAncestor or more likely don't > >> understand how it should work. In either case, my displayPageStandard > >> for dmHTML looks like the following: > >> > >> <!--- Not Cached ---> > >> <skin:view typename="dmHTML" template="checkHTTPS" https="0"> > >> > >> <!--- Cached ---> > >> <skin:view objectid="#stobj.objectid#" typename="#stobj.typename#" > >> template="displayHeaderStandard" /> > >> > >> <!--- Not Cached ---> > >> <skin:view webskin="displayLoggedInHeader" typename="dmHTML" /> > >> > >> <!--- Cached ---> > >> <skin:view objectid="#stobj.objectid#" typename="#stobj.typename#" > >> template="displayCachedPageStandard" /> > >> > >> <!--- Cached ---> > >> <skin:view objectid="#stobj.objectid#" typename="#stobj.typename#" > >> template="displayFooterStandard" footerIndent="0" /> > >> > >> > >> Basically, three views are cached, two are not, according to the cfc > >> for dmHTML. Now, looking at my dmWebskinAncestor, it is growing fast, > >> because it appears to be loading into the table every call to the > >> checkHTTPS skin. Interestingly enough, the displayLoggedInHeader, > >> which is also not cached, is not being called into dmWebskinAncestor. > >> Any reason for this to happen? Luckily, this site does not have major > >> traffic, but it nonetheless fills up the dmWebskinAncestor table > >> quickly. > >> > >> I guess my question is two fold: > >> > >> 1) Is it ok to truncate the table upon restarting the application, > >> with the idea that the application then loads everything again. > >> 2) What exactly does the table do? Is it a check for the cache to see > >> what files it needs to load up next? > >> > >> Any help in this regard is appreciated, > >> > >> Tomek > >> > >> > > >> > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "farcry-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/farcry-dev?hl=en -~----------~----~----~----~------~----~------~--~---
