randgen team mailing list archive
-
randgen team
-
Mailing list archive
-
Message #00157
Re: --sqltrace: OK to mark bad queries?
-
To:
randgen@xxxxxxxxxxxxxxxxxxx
-
From:
John Embretsen <johnemb@xxxxxxxxx>
-
Date:
Fri, 11 Nov 2011 09:07:52 +0100
-
In-reply-to:
<CALHfRv=cyxyb7ubTu5Vaa+D0_qtsF44x3FdgX+bvYVgzXMCO=w@mail.gmail.com>
-
User-agent:
Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
On 09/29/2011 10:26 AM, John H. Embretsen wrote:
Hi,
The suggested changes are now in the randgen tree on Launchpad. See
revid john.embretsen@xxxxxxxxxx-20110928192605-7ffumru4ipcja7h0.
http://bazaar.launchpad.net/~randgen/randgen/rqg2/revision/836.3.21
Invalid queries are now prefixed with
# [sqltrace] ERROR<errno>:
when using --sqltrace and the MySQL executor.
Based on some feedback I have made this new behavior optional:
--sqltrace will print all statements, no extra prefixes or markings.
--sqltrace=MarkErrors will print all statements, but prefix "invalid"
statements with the string mentioned above.
This is so that it would be possible to retain the old behavior for
users who use the SQL trace to reproduce issues that depend on
statements that cause errors or crashes.
This change will likely be merged to the randgen Launchpad branch soon
(revid john.embretsen@xxxxxxxxxx-20111111073859-oxikhqbgn2a9gw7o).
--
John
References