epigramx

I'd be interested in that feature as well. Unfortunately I don't have a Wiimote Plus, only a regular one so I could not help much in editing. Ideally the library...

What I don't get is why does it do it for each package separately. E.g. it's slow to go from 0/11 to 1/11 and then it still takes time for...

I believe this area is more of a problem to be allowed to exist as it is compared to having a basic solution first before developing a more complex list...

By the way: the nature of the problem might be worse than just being related to performance. Because of the slowness (even when tested on a fast PC), it appears...

Yeah I also suspect it's out of your hands in which case it would need to take it to either sqlalchemy devs or sqlite devs but that would need good...

I would only be able to say "sqlite slow but postgres fast" which is hard to debug or prove it's a bug. It could be normal that postgres itself is...

Taking 2.3 seconds to take 500 entries from a table of this (low-ish) complexity sounds pretty suspect. Here it's almost unusable because it may take so long at the dashboard...

There is an index but it can not be used to replace offsetting because if an entry is deleted: that index remains at its original value, so a new column...

I'm half-following your conversation with the sqlalchemy devs and `lazy="select"` is indeed ludicrously faster here (we're talking about a total response of only 3 to 5 seconds now without changing...

They seem certain `OFFSET` should be avoided one way or another. I noticed their page for situations like this . I guess at least the final method is applicable which...