in reply to Listing # comments versus # replies

Without knowing much about the site's internals, I would have to speculate that such a feat would require recursively walking the database for each top-level node being displayed, to identify how many total replies and replies to replies have occurred. My guess is that would have an exponential effect on the amount of server load for page loads that contain many top-level nodes with many nth level followups.


Dave

  • Comment on Re: Listing # comments versus # replies

Replies are listed 'Best First'.
Re: Re: Listing # comments versus # replies
by PodMaster (Abbot) on Feb 29, 2004 at 16:52 UTC
    Nope. If you can, see for yourself => newlistapproved ( the sql looks like "select count...").

    update: It appears there is some support for this already, but the user setting is missing? I'll investigate.
    update: And patch submitted (The dangerous Signature Settings had it, but User Settings didn't).

    MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
    I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
    ** The third rule of perl club is a statement of fact: pod is sexy.

[reply]
      Cool deal. As to the grandparent post, I considered that possibility , but I figured the PerlMonks gods were smarter than that given the relatively decent speed at which pages load today... :)

      FYI -- I don't think we have permision to see the nodes you linked, so we will just pretend they had cool stuff on them :)

[reply]

        Actually its not so cool. You aren't missing much. :-)


        ---
        demerphq

          First they ignore you, then they laugh at you, then they fight you, then you win.
          -- Gandhi
[reply]
[d/l]

In Section Perl Monks Discussion