Closed GoogleCodeExporter closed 9 years ago
Yeah, I see the problem, but these parameters log4jdbc.dump.sql.* were a bad
idea from the beginning (the original developer of log4jdbc himself said he
thought about disabling this feature, see
https://code.google.com/p/log4jdbc/issues/detail?id=28)
I think this could be implemented in a custom RdbmsSpecifics, or something
similar, so that users could define what is a select statement, an update
statement, etc. But this would require some work. Unless you could come up with
a patch, I think this will remain a "won't fix".
Original comment by frederic...@gmail.com
on 31 Jan 2015 at 11:01
Original issue reported on code.google.com by
dmitry.k...@gmail.com
on 19 Nov 2014 at 1:49