We're updating the issue view to help you get more done. 

Query "Results Per Page" broken if user includes all caps LIMIT keyword

Description

Wilbert Kraan pointed out this issue: http://sourceforge.net/mailarchive/forum.php?thread_name=9F8E44BC27E22046B84EC1B9364C66A1A399E734E6%40EXCH07-4850.ida.org&forum_name=sesame-general

Investigation yeilded the cause as lying in the PagedQuery class. While a RegEx correctly finds the LIMIT expression regardless of case, the logic for performing server side substitution in the query only works correctly if the all-lower-case version of the 'limit' keyword was used.

This should be an easy fix. Workaround at present: use all-lower case for the 'limit' keyword in your queries.

Environment

None

Status

Assignee

Dale W. Visser

Reporter

Dale W. Visser

Labels

Components

Fix versions

Affects versions

2.7.2
2.7.0
2.7.3
2.7.1

Priority

Minor