New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

The problem about option 'log4jdbc.trim.sql.extrablanklines' #47

Open

GoogleCodeExporter opened this issue Mar 30, 2015 · 1 comment

Labels

auto-migrated Priority-Low Type-Defect

GoogleCodeExporter commented Mar 30, 2015

If the option 'log4jdbc.trim.sql.extrablanklines' is true, then the output sql 
will be end with a char '\n'. I think it's better to remove it. :) What do you 
think? Thanks.

Original issue reported on code.google.com by ihuangwj on 15 Mar 2012 at 6:33

The text was updated successfully, but these errors were encountered:

Author

GoogleCodeExporter commented Mar 30, 2015

I would think that if there is a final newline at the end in the original SQL, 
it should be passed through.  But I can see how it might be nice to have a new 
option to suppress any trailing newline.

Original comment by [email protected] on 22 Mar 2012 at 1:25

Added labels: Priority-Low
Removed labels: Priority-Medium

GoogleCodeExporter added Type-Defect auto-migrated Priority-Low labels

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment