As a performance update we only use refObjects where we have to -- ie. when you don't know the typename of the object you are accessing. For most system objects used in core, we know exactly what typename we are working with so we don't need to store the typename in refObjects.
So the messages you see there are simply warnings saying that refObjects lookups have been deactivated for the typename in question. Hope that helps, -- geoff http://www.daemon.com.au/ On 4 October 2010 20:25, smika <[email protected]> wrote: > Dear friends, > > after fixing bugs in arminfo.am application on hostek server, i've > mention that during FixRefObjects table i am getting messages like > this: > > Started dmWebskinAncestor > IGNORED dmWebskinAncestor - bRefObjects has been set to false. > RefObjects cleared. > > Started dmWizard > IGNORED dmWizard - bRefObjects has been set to false. RefObjects > cleared. > > Started farLog > IGNORED farLog - bRefObjects has been set to false. RefObjects > cleared. > > What does this mean? > > Thanks, > > Mika -- You received this message cos you are subscribed to "farcry-dev" Google group. To post, email: [email protected] To unsubscribe, email: [email protected] For more options: http://groups.google.com/group/farcry-dev -------------------------------- Follow us on Twitter: http://twitter.com/farcry
