Hi Fernand, > Frank, are you telling that after opening a table and after we scroll > to the last record, (I suppose we have the content off the table now in > memory) the search go's back to the Server to find a result ?? and the > search is not using the resultset already present in the memory off the > local machine ?
We do not cache the complete result set. There is a client-side cache, which control how many records are *completely* held in memory. This is defaulted to 50 rows, or "2*visible rows" if there's a grid control involved. Other than that, we only cache values which uniquely identify a row (the PK, or a unique index field, or a bookmark). > BTW: filtering is done where ? On the server: a new SQL statement is created, including the filter, and all data is completely re-fetched. Even if Base would cache the complete data, filtering would still be faster (assuming a reasonable connection to the server), since the server usually knows best how to organize its data for quick access/filter/search (e.g. if you defined an index for a column, and filter for those col's values). Ciao Frank -- - Frank Schönheit, Software Engineer [email protected] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
