Great diagnosis!

In fact, it was this small change that broke all node sets that were user lists and should reflect the "recent" users:

Originally, there was this query, which did not use an index on lasttime:

                SELECT node_id    pick_id,
                       title      pickname,
                       node_id    auth_id,
                       title      authname,
                       experience rep
                  FROM node,
                       user
                 WHERE node_id = user_id
                  AND (UNIX_TIMESTAMP(NOW()) - UNIX_TIMESTAMP(lasttime
+) < ?)
              ORDER BY experience $args{order},
                       node_id ASC
                LIMIT  $limit
[download]

I eliminated the function on lasttime by converting the date math from math on integers/unix timestamps to math on datetime types:

                SELECT node_id    pick_id,
                       title      pickname,
                       node_id    auth_id,
                       title      authname,
                       experience rep
                  FROM node,
                       user
                 WHERE node_id = user_id
                   AND lasttime > date_sub(NOW(), INTERVAL ? DAY)
              ORDER BY experience $args{order},
                       node_id ASC
                LIMIT  $limit
[download]

which now used days where it should have used seconds:

                SELECT node_id    pick_id,
                       title      pickname,
                       node_id    auth_id,
                       title      authname,
                       experience rep
                  FROM node,
                       user
                 WHERE node_id = user_id
                   AND lasttime > date_sub(NOW(), INTERVAL ? SECOND)
              ORDER BY experience $args{order},
                       node_id ASC
                LIMIT  $limit
[download]

As my excuse, there was a similar-yet-different code path further above, where the same parameters were used for non-user nodes that were in days, instead of seconds :-)).

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.