Skip to content

Commit

Permalink
No commit message
Browse files Browse the repository at this point in the history
  • Loading branch information
buruzaemon committed Dec 26, 2010
1 parent 0b6bb54 commit 118312e
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions README.rdoc
Original file line number Original file line Diff line number Diff line change
Expand Up @@ -25,8 +25,8 @@ Sybase is an awful DB in term of support for "offset". I found 2 ways to do it f
select * from #tt_sorted ORDER BY <original order> select * from #tt_sorted ORDER BY <original order>


There are 2 major drawbacks here. There are 2 major drawbacks here.
1. If the offset is a large number, the space taken by the temptable can fill up the tempdb. 1. If the offset is a large number, the space taken by the temptable can fill up the tempdb.
2. The original query should be parsed to strip out "ORDER BY" 2. The original query should be parsed to strip out "ORDER BY"


=== 2. Use a scrollable cursor: === 2. Use a scrollable cursor:


Expand All @@ -49,8 +49,8 @@ There are 2 major drawbacks here.
deallocate crsr deallocate crsr


The problems here are: The problems here are:
1. Scrollable cursor works for Sybase ASE starting from version 15. 1. Scrollable cursor works for Sybase ASE starting from version 15.
2. Cursors are not very efficient in Sybase ASE, and very inefficient in Sybase IQ. 2. Cursors are not very efficient in Sybase ASE, and very inefficient in Sybase IQ.


I am not a Sybase expert, so *Please let me know if you are aware of more efficient ways to do limit and offset.* I am not a Sybase expert, so *Please let me know if you are aware of more efficient ways to do limit and offset.*


Expand Down

0 comments on commit 118312e

Please sign in to comment.