On Jan 14, 2008, at 3:58 AM, pepone.onrez wrote:
I have this query in a table with 150 thowsand tuples and it takes
to long
t_documentcontent._id AS _id
FROM t_documentcontent LIMIT 50 OFFSET 80000
You want an ORDER BY there. Not only will it probably speed things
up, without it there's no guaranteed order in the results returned.
As table records have no specific order and updates and inserts on
that table take the first free position, you risk ending up showing
some records twice in your set (same id on different 'pages') and
missing others because you've already skipped past them when there's
concurrent access.
There's still some risk for that if you order, but as you seem to
order on a sequence-generated column, updates aren't a problem for
you and inserts end up at the end anyway. But only if you order them.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.
!DSPAM:737,478f1e139491365710960!
---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
