Hi, it seems that Queries with ORDER BY (and a LIMIT-Clause to keep the result small) are quite slow if the ORDER BY is on an INTEGER PRIMARY KEY - column. If the ORDER BY is on a normal column for which I made an index, its quite fast.
It doesn't help do create an index on the primary key (doesn't make sense since its already there, does it?). Hav you got any explanations? Is this an expected behaviour or is it just a bug? The workaround is, of course, not to declare columns as INTEGER PRIMARY KEY if you want do ORDER BY them. Sebastian Setzer
