les-mockingjay / log4jdbc-log4j2

Automatically exported from code.google.com/p/log4jdbc-log4j2
0 stars 0 forks source link

StatementSpy.addBatch() does not respect Properties.isStatementUsageWarn() #18

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Set  log4jdbc.statement.warn  to false in properties
2. Call StatementSpy.addBatch()

What is the expected output? What do you see instead?
Do not expect to see "{WARNING: Statement used to run SQL}"
But do see "{WARNING: Statement used to run SQL}"

What version of the product are you using? On what operating system?
log4jdbc-log4j2-jdbc4.1-1.16

Please provide any additional information below.
reportStatementSql() has this:

_reportSql((Properties.isStatementUsageWarn()?StatementSqlWarning:"") +
                sql, methodCall);

But addBatch() just has:

currentBatch.add(StatementSqlWarning + sql);

Original issue reported on code.google.com by jst...@tnsi.com on 28 May 2014 at 4:58

GoogleCodeExporter commented 9 years ago

Original comment by frederic...@gmail.com on 4 Jun 2014 at 11:56

GoogleCodeExporter commented 9 years ago
Thanks for reporting this. It has been fixed in release 1.17-SNAPSHOT

Original comment by frederic...@gmail.com on 5 Jun 2014 at 1:34