Re: [vassalengine-devel] stable and unstable releases

[Bsmith <bs...@ne...>]

Ah ok.  What would really help is having the database do all of the collation using a (more) sophisticated query;  So the final data to be displayed in the Server window would simply be the records returned to the script from that query.  It's generally a good idea to have the DB do as much of the data crunching as possible.

So yeah, I guess the script needs to be made more efficient as you said  :)

-----Original message-----
From: "Rodney Kinney" rod...@co...
Date: Fri, 21 Dec 2007 07:13:30 +1100
To: "developers' list for VASSAL" vas...@li...
Subject: Re: [vassalengine-devel] stable and unstable releases

> Actually, I described a previous version of the Connection History link.
> The current script does store and query MySQL for the connection history.
> The script periodically deletes rows older than a month and returns the
> entire list when asked for the history.  Because it's always pulling all of
> the rows from the table, an index wouldn't help.  I suspect that most of
> time is spent on the client side collating all of the data.
> 
> rk
> 
>