randgen team mailing list archive

[Patrick Crews <gleebix@xxxxxxxxx>]

Roel,

At the risk of sounding flippant - "Good God, No" ; )

It can be pretty tricky to 'dial-in' a grammar to generate interesting *and*
valid queries, so we often limit a grammar to a targeted area.

To get an idea of how complex a grammar can be, I suggest looking at the
optimizer_subquery grammars.  Just trying to produce *some* nasty subqueries
is a hairy mess (of course, it was also one of my first stabs at grammar
writing...).  Grammar writing is often a trade-off between variety and
validity (ie if we try to cover a lot of ground, we are also likely to
produce a higher percentage of queries that are short-circuited before
exercising any interesting code - like WHERE 'a' = 1 or somesuch)

Also, the way the randgen works, we would have to run a test for a *very*
long time to ensure that you cover everything (ie that the randgen hits
enough of the possible queries).  It just tends to make more sense to write
smaller grammars that focus on certain areas.

Hope this information helps,
Patrick

On Thu, Dec 30, 2010 at 6:37 PM, Roel Van de Paar <
roel.van.de.paar@xxxxxxxxxx> wrote:

>  Hi!
>
> I am interested to know if there was ever(/is) an "all-inclusive" test
> (grammar/config file) created for testing MySQL with RQG, or something that
> came close to it.
>
> With "all-inclusive" I mean a test (grammar/config file) that test every
> area/aspect of the server (or at least many/several), but from one test
> instead of many different tests spread across many files.
>
> Kind Regards,
> God Bless,
> --
> Roel Van de Paar, Senior Technical Support Engineer
> MySQL @ Oracle Corporation, Asia-Pacifichttp://www.mysql.com
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~randgen<https://launchpad.net/%7Erandgen>
> Post to     : randgen@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~randgen<https://launchpad.net/%7Erandgen>
> More help   : https://help.launchpad.net/ListHelp
>
>