flysa / log4jdbc

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

parameter log4jdbc.dump.sql.maxlinelength value is not recognized except 0 #11

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. set log4jdbc.dump.sql.maxlinelength=20
2. enable logging with sql statements

What is the expected output? What do you see instead?
The logged sql statement should break after the next space after 20
characters, but still break after 90 characters.

What version of the product are you using? On what operating system?
current repository revision 63/1.2 alpha2

Patch to fix this is attached.

Original issue reported on code.google.com by c...@forty2.de on 13 Aug 2009 at 3:22

Attachments:

GoogleCodeExporter commented 8 years ago
Oops!  Fixed now on trunk, SVN rev 68.

Original comment by arthur.b...@gmail.com on 2 Dec 2009 at 8:00