| [news.eclipse.platform.swt] Re: Huge table, records, scrolling, etc. |
Mr. Burns wrote: > Hello, > thanks for reply, > > I know already to cache some records, to avoid a SELECT * statement sent > to database every time the SetData trigger is executed. This is already > clear. And how many records I should cache I can easily test with try and > error. But my question is HOW should I cache??? > Should I use a vector to holde e.g. 25 records, or should I use a 2nd non > virtual table and copy to the virtual table if next 25 records are > requested to be visible? Or are ther other possibilities? What are the > pros and cons of using vector / non virtual table / etc. ? > > Thanks for further discussion! Mr. Burns, i extend AbstractList (you have to implement only get(int i)) method in class I load xxx (default for me 30) rows from tbale and remember that is from row x to row y in base - when client seek row out of x to y i load new 30 rows from database regards