all,
thanks to all for the feedback, it was certainly useful. it's not as top
prioriy, but i think i will want to work on this if i have time. fyi,
for this case i'm using postgresql.
Gene Amtower wrote:
Burak,
I brushed over your original post without responding, but Michael's
response g
I use Oracle.
It is unbeliavable performance when paging or sorting. In milli seconds, i
see the data on paging.
Qx0.7.2, IE6, Oracle 9i/10g.
I also use the remote table with default page limit & offsets.
What is your database? Oracle uses something lke rownum and rowid features
helped me lot.
Burak,
I brushed over your original post without responding, but Michael's
response got me to thinking about it again. I believe the LIMIT and
OFFSET clauses are the correct way to approach this problem - any
performance issues with this query statement format reside appropriately
with the databa
Hi Burak,
I tried to do that initially. However, it seemed to me that this is only
a viable solution if data gets sorted by id. Everything gets quite
complicated if you try to sort a table by other entries, e.g.
alphabetically, let's say by a column named "title". Then you would have
to save t
all,
the current method to produce responses to remote table models is to use
the underlying database's limit & offset method. while being the
simplest solution, offsetting is either
1) slow
2) fast when the query is cached on the server side, but then it's
costly in memory.
i don't think thi
