On Fri, Nov 30, 2007 at 12:02:23PM -0700, m h wrote:
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
This one is fixed now. The offset handling without limit was missing.
Niels
SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users