Re: [Gitstat-devel] [bug 1785778] sql query to get the maximum commits

Hi,
gitstat has not only some bugs but also many trivial bugs, you know.
Actually, we need helping hand like you.:)
you gave me good query string, so I could modify easily,
I'll handle this issue like your comment.

Thanks,

On 9/3/07, Paul Vriens <pau...@gm...> wrote:
> Hi,
>
> (This relates to bug 1785578 'ybase is set fixed for "number of changesets" graph')
>
> I've figured out the sql statement to get the maximum number of commits in the
> changeset:
>
> mysql> select max(maxcommits) from (select
> count(DATE_FORMAT(FROM_UNIXTIME(commitdate),'%Y%m%d')) as maxcommits
> from ChangeLog group by
> DATE_FORMAT(FROM_UNIXTIME(commitdate),'%Y%m%d')) as t1;
> +-----------------+
> | max(maxcommits) |
> +-----------------+
> |             733 |
> +-----------------+
> 1 row in set (0.22 sec)
>
> You see even the '700' that is currently set for the linux kernel is not enough ;-)
>
> Apart from that if you browse to the current gitstat page
> (http://tree.celinuxforum.org/gitstat/chart.php?chart_parameter1=1&submit=1&setybase=700&prevperiod=16)
> you'll also see that 700 is not correct.
>
> One thing we could do is use the outcome from the above sql query, round that up
> to a nice number and set that as ybase? The downside is that we have to execute
> the query for every page (chart.php?chart_parameter1=1) as it's not 'globally' used.
>
> Cheers,
>
> Paul.
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> Gitstat-devel mailing list
> Git...@li...
> https://lists.sourceforge.net/lists/listinfo/gitstat-devel
>