mongo-ruby-driver/lib/mongo
asinbow.wang 56968e8ad3 fix log debug level detect
* reason
  there hardcodes DEBUG_LEVEL in logging.rb:
    DEBUG_LEVEL = defined?(Logger) ? Logger::DEBUG : 0
  this could cause some incompatibility between different logger tools

  for Logger, DEBUG/0 < INFO/1 < WARN/2 < ERROR/3 < FATAL/4,
  for Log4r,  ALL/0 < DETAIL/1 < DEBUG/2 < INFO/3 < WARN/4 < ERROR/5 < FATAL/6.

  anyway, it is not in good pattern.

* suggestion
  logger.debug { ... }
  if current level is greater than DEBUG, the block will not be
  evaluated. it is also efficient.

  following is also supported by most loggers.
  logger.info { ... }
  logger.warn { ... }
  logger.error { ... }
  ...
2012-04-27 15:26:49 +08:00
..
gridfs RUBY-422 Cleanup testing output 2012-03-16 16:17:33 -04:00
util fix log debug level detect 2012-04-27 15:26:49 +08:00
collection.rb RUBY-422 Cleanup testing output 2012-03-16 16:17:33 -04:00
connection.rb minor: refactor TCP_NODELAY 2012-04-08 10:48:25 -04:00
cursor.rb RUBY-416 do not checkout closed sockets 2012-03-07 12:00:10 -05:00
db.rb RUBY-429 non-blocking IO for socket timeouts 2012-04-03 16:06:37 -04:00
exceptions.rb RUBY-429 non-blocking IO for socket timeouts 2012-04-03 16:06:37 -04:00
networking.rb RUBY-429 non-blocking IO for socket timeouts 2012-04-03 16:06:37 -04:00
repl_set_connection.rb minor: test cleanup 2012-04-04 13:51:04 -04:00
version.rb RELEASE 1.6.2 2012-04-05 13:51:20 -04:00