MSSQL3Adapter & MSSQL3NAdapter combination of orderby and limitby resulting in a wrong sql query

db.define_table('tag', Field('title', 'string'),)

tags = db(db.tag.id > 0).select(
                      db.tag.id,
                      db.tag.title,
                      orderby=db.tag.title|db.tag.id,
                      limitby=(1,40),
                      )

print db._lastsql

SELECT  f_0, f_1 FROM (SELECT  ROW_NUMBER() OVER (ORDER BY tag.id, tag.title) AS w_row, tag.id AS f_0,  tag.title AS f_1 FROM tag WHERE (tag.id > 0) ) TMP WHERE w_row BETWEEN 2 AND 40;

in OVER (ORDER BY tag.id, tag.title) the order of the statements is wrong, it seems id is always first. I found the bug because SQLFORM.grid messed up the column sorting in pages > 1.

[niphlod]

@gi0baro : remember this, should be addressed as soon as the new “overhaul” branch gets polished

[gi0baro]

@skoa-h I’m closing this since should be fixed in the current master