Boolean Chart Redesign

[Bradley Baetz]

On Tue, Jul 20, 2010 at 2:35 PM, Bernd Groh <bgroh at redhat.com> wrote:
> Completely agree. Though I believe people indeed care how they can use the
> URL in order to query bugzilla. I know a lot of people who don't use the UI,
> but use the URL directly (me included), and for these people, the easier
> they can represent a boolean string, the easier it is.

So this has been a problem pretty much from day one. (Bugzilla used to
support a URL param of sql=<foo> which it injected directly into the
query to allow custom 'stuff'. This was not exactly secure (to say the
least...) and was removed about eight years ago)

The problem with being too generic is that MySQL's query optimiser
sucks in a lot of respects, especially older versions which many
people are running. In the boolean charts context, that's most likely
to be around how MySQL does joins (basically, one index per table per
query, so joining bugs to too many child tables causes full table
scans). Its going to need a fair bit of careful design to end up with
SQL that works well on large DBs.

Bradley