Would like to have logger.emtpy_line; and logger.empty_line(3)

[JuergenSchuster]

Enhancement. Now I have to do logger.log(' '); not so nice to read

[jeffreykemp]

I'd do something like logger.log('HEARTBEAT'); so it doesn't look like an error.

[martindsouza]

@JuergenSchuster I'll need a good reason and many up votes to add such a command to the API when you can do logger.log(null). Can you please provide the use case?

For now I'll tag it as a future.

[JuergenSchuster]

@martindsouza It's not a big deal. I think we agree to have blank lines to structure your logging outputs.

logger.log(null) is not an option, people need to think about it, what this actually does (remember there are normal people programming PL/SQL too :-)

logger.log(' '); Everybody understands immediately, but it is not nice.

logger.empty_lines(3); would be fantastic to read :-)

[martindsouza]

@JuergenSchuster If we du have an empty_lines API how do we specify the level it gets logged at?

[JuergenSchuster]

@martindsouza Debug level only

[janihur]

@JuergenSchuster I fail to see why one would like to log "nothing". Is the purpose to record a wall clock time of the program execution ? But the logger have dedicated timing methods.

[jeffreykemp]

Or is it to add breaks in the log for reporting/printing? In which case I'd do logger.log('--');

However, I think the whole purpose of a debug log is to log something.