X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=dbsrgits%2FDBIx-Class-DeploymentHandler.git;a=blobdiff_plain;f=lib%2FDBIx%2FClass%2FDeploymentHandler.pm;fp=lib%2FDBIx%2FClass%2FDeploymentHandler.pm;h=f9b11fe526fdb436d9cac0d497cafe73ce34d69b;hp=fc2ebad9a6614bddd16d6f331b499b97513ae701;hb=8465e76797613fa0b9c85365c03d26cacbaab31a;hpb=e77651a89c60e38bd3f81da8a98084ca9160110c

diff --git a/lib/DBIx/Class/DeploymentHandler.pm b/lib/DBIx/Class/DeploymentHandler.pm
index fc2ebad..f9b11fe 100644
--- a/lib/DBIx/Class/DeploymentHandler.pm
+++ b/lib/DBIx/Class/DeploymentHandler.pm
@@ -188,18 +188,17 @@ Now you should be able to use C<DBIx::Class::DeploymentHandler> like normal!
 =head1 LOGGING
 
 This is a complex tool, and because of that sometimes you'll want to see
-what exactly is happening.  The best way to do that is to use the built
-in logging functionality.  Currently three of the standard five log levels
-are used; C<info>, C<debug>, and C<trace>.  Info will typically just print
-out when methods that actually change things along with the most important
-args to the method.  Debug will give you a little bit more information,
-for example debug will currently tell you which files are being run when
-a migration is being called.  Trace of course goes even further.  It will
-actually give you the SQL or Perl code being executed when a migration is run.
-
-To enable the various logging levels all you need to do is set some environment
-variables: C<DBICDH_INFO>, C<DBICDH_DEBUG>, and C<DBICDH_TRACE>.  Each level
-can be set on it's own, so you can turn on trace without turning on info.
+what exactly is happening.  The best way to do that is to use the built in
+logging functionality.  It the standard six log levels; C<fatal>, C<error>,
+C<warn>, C<info>, C<debug>, and C<trace>.  Most of those are pretty self
+explanatory.  Generally a safe level to see what all is going on is debug,
+which will give you everything except for the exact SQL being run.
+
+To enable the various logging levels all you need to do is set an environment
+variables: C<DBICDH_FATAL>, C<DBICDH_ERROR>, C<DBICDH_WARN>, C<DBICDH_INFO>,
+C<DBICDH_DEBUG>, and C<DBICDH_TRACE>.  Each level can be set on it's own,
+but the default is the first three on and the last three off, and the levels
+cascade, so if you turn on trace the rest will turn on automatically.
 
 Lastly, the logging uses L<Log::Contextual>, so if you have already set up an
 application-wide logger this will use that logger instead, and the environment