Frank Schönheit - Sun Microsystems Germany wrote:
Hi Fernand,
Thanks for this quick fix, now I have a other "performance" problem:
When have a table opened (all content in memory) or wehave the content
in a Beamer then the search is very... very... slow compared to wath we
can do in the original MySQL tables or compared to a ohter frondend
application.
This probably is the very same bug:
?? I do not think it is related to the driver, we have this slowness
with every Database not only with MySQL
Okay, I got you wrong here, should have read more carefully :) I assume
that you were talking about bad performance native vs. ODBC driver.
Not sure we already have a performance bug for the search, you might
want to submit one. However, there's a certain limit which we cannot
break: Due to the nature of this searching, all data has to be fetched
from the server,
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 ?
BTW: filtering is done where ?
so it's surely slower than server-side filtering. Which
doesn't mean there's no room for improvement in the client-side
searching ...
Ciao
Frank
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
