incubator-bloodhound-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary <gary.mar...@wandisco.com>
Subject Re: [Apache Bloodhound] #30: Default report {7} My Tickets fails for issues.apache.org/bloodhound configuration
Date Wed, 11 Apr 2012 18:19:30 GMT
Finally.. the reason that I decided to improve the documentation a 
little for MySQL was this ticket that I raised earlier. As there are 
some indications how to fix this in the Trac ticket, I was wondering if 
someone else would be interested in looking into this.

Cheers,
     Gary

On 04/11/2012 01:15 PM, Apache Bloodhound wrote:
> #30: Default report {7} My Tickets fails for issues.apache.org/bloodhound
> configuration
> -----------------------+-------------------------------------
>   Reporter:  gjm        |      Owner:  nobody
>       Type:  defect     |     Status:  new
>   Priority:  major      |  Milestone:  RC1 for initial release
> Component:  trac core  |    Version:
>   Keywords:             |
> -----------------------+-------------------------------------
>   Error is: {{{ProgrammingError: for SELECT DISTINCT, ORDER BY expressions
>   must appear in select list}}}
>
>   I have already modified the report SQL for the
>   issues.apache.org/bloodhound (hopefully correctly) but this does not deal
>   with the underlying problem. The error has already been noted, with
>   possible fixes in trac:comment:13:ticket:9311
>
>   I suspect that we will need to modify trunk/trac/trac/db_default.py to
>   provide non-erroring sql for this report and test across all supported
>   databases.
>


Mime
View raw message