On Nov 27, 2007 2:40 PM, m h <sesquile@gmail.com> wrote:
It appears that the "ORDER BY" is throwing things off. Bug? This bug is fixed now. Both the case with and with out order by gave wrong results. It needed some work in the optimizer which was push 'renumber' statements down the tree which doesn't work with offsets.
(only available from cvs tho).
Still has a bug. OFFSET by itself (without a LIMIT clause) doesn't work correctly. The second query here should only return (3,ed)...(7,fido) sql>select * from query_users ; +---------+----------+ |user_id |user_name | +=========+==========+ | 1 |john | | 2 |jack | | 3 |ed | | 4 |wendy | | 5 |laura | | 6 |ralph | | 7 |fido | +---------+----------+ sql>select * from query_users OFFSET 2; +---------+----------+ |user_id |user_name | +=========+==========+ | 1 |john | | 2 |jack | | 3 |ed | | 4 |wendy | | 5 |laura | | 6 |ralph | | 7 |fido | +---------+----------+ Have opened bug 1841896