High archive page numbers cause invalid database queries

[Viper007Bond]

Visiting http://www.viper007bond.com/category/videos/page/6805063692754011230 on my site generates the following database query:

SELECT SQL_CALC_FOUND_ROWS wp_posts.ID FROM wp_posts INNER JOIN wp_term_relationships ON (wp_posts.ID = wp_term_relationships.object_id) WHERE 1=1 AND ( wp_term_relationships.term_taxonomy_id IN (21) ) AND wp_posts.post_type = 'post' AND (wp_posts.post_status = 'publish' OR wp_posts.post_status = 'private') GROUP BY wp_posts.ID ORDER BY wp_posts.post_date DESC LIMIT 6.805063692754E+19, 10

Note the scientific notation LIMIT value.

PHP: 5.3.15-pl0-gentoo
MySQL: 5.2.12
WordPress: r23386

[Viper007Bond]

Interestingly I cannot reproduce this locally, so it may be 32bit vs 64bit or something. The same paged value results in this query:

SELECT SQL_CALC_FOUND_ROWS wp_trunk_posts.ID FROM wp_trunk_posts INNER JOIN wp_trunk_term_relationships ON (wp_trunk_posts.ID = wp_trunk_term_relationships.object_id) WHERE 1=1 AND ( wp_trunk_term_relationships.term_taxonomy_id IN (1) ) AND wp_trunk_posts.post_type = 'post' AND (wp_trunk_posts.post_status = 'publish' OR wp_trunk_posts.post_status = 'private') GROUP BY wp_trunk_posts.ID ORDER BY wp_trunk_posts.post_date DESC LIMIT 21474836460, 10

No idea where this other LIMIT is coming from.

[nacin]

2147483647 is the maximum integer (signed) on 32 bit systems.

[SergeyBiryukov]

Replying to Viper007Bond:

No idea where this other LIMIT is coming from.

Caused by absint() in WP_Query::parse_query():
​http://core.trac.wordpress.org/browser/tags/3.5.1/wp-includes/query.php#L1449

[wonderboymusic]

23383.diff​ adds an optional 2nd param to absint( $maybeint, $limit = false ) that, if set to true, will only return up to PHP_INT_MAX

[SergeyBiryukov]

Related: #28559

[pbearne]

I feel we should return 0 not max_int as this is more likely to tested for as an error this is what string / errors current return

Max_int will diff on 32 and 64 bit systems

paul

[wonderboymusic]

In 28855:

Add a second optional parameter to absint() to limit the result to PHP_INT_MAX.

See #23383.

[wonderboymusic]

In 28856:

absint() should always return PHP_INT_MAX if the resulting value exceeds it.

See [28855].
Fixes #23383.

[nacin]

No. No, absolutely not. Why slow down this function?

An aside, does this even work? When can an integer ever be greater than PHP_INT_MAX?

[wonderboymusic]

In 28857:

Revert [28856] at nacin's behest. See #23383.

[nacin]

To be clear, I would like to see [28855] reverted too.

Incidentally, this has the potential to break things when absint() is attached to a filter that passes more than one argument. But my real objection is this is absurd to fix, at least in this way, inside this generic function.

[SergeyBiryukov]

[28858] missed the ticket.

[nacin]

I don't think this can't be solved in some regard for some situations, I just don't think absint() is the right level.

Example: Convert $qpaged from a string to a float, then see if it is greater than the maximum integer. (I believe this works.) Handle it specifically for pagination.

Another option is to look into handling this inside wpdb->prepare() for %d, though I'm not sure.

[SergeyBiryukov]

I can reproduce the issue on a shared hosting, and 23383.2.diff​ fixes it for me.

I've tested other query vars, and they don't have this issue.

[SergeyBiryukov]

In 28864:

Make sure the first number in LIMIT clause in WP_Query::get_posts() is always an integer.

fixes #23383.

[pbearne]

Have look at the patch in #28559 to see the edge cases