DBI error messages can include full SQL

[GoogleCodeExporter]

There's some setting for DBI as I recall that makes it print out the whole
SQL it tried to exec when there's an error.  I mean it throws it as part of
the error.

If we enable this in DSNParser, will it royally mess anything up?

Original issue reported on code.google.com by baron.schwartz on 6 Oct 2008 at 1:25

[GoogleCodeExporter]

Peter has added his vote to this:

[percona@my1 ~]$ mk-table-checksum --replicate=adserver.mkchecksum 
--createreplicate
--sleep-coef=1 localhost --user root
DBD::mysql::db selectrow_hashref failed: Unable to open underlying table which 
is
differently defined or of non-MyISAM type or doesn't exist at
/usr/local/bin/mk-table-checksum line 1669.

This applies to merge table... Well I'd really like to know what table
it  was  -  I think it is very good to print the query which failed to
execute.

Original comment by baron.schwartz on 6 Apr 2009 at 2:41

[GoogleCodeExporter]

Original comment by baron.schwartz on 4 May 2009 at 2:13

• Added labels: Tool-all

[GoogleCodeExporter]

Original comment by baron.schwartz on 7 Jun 2009 at 8:38

• Added labels: CodeCleanup

[GoogleCodeExporter]

Done in r4103 and r4105.

Original comment by dan...@percona.com on 8 Jul 2009 at 7:09

• Changed state: Fixed