--- PApp-SQL/SQL.pm	2001/01/06 03:04:03	1.5
+++ PApp-SQL/SQL.pm	2001/01/07 02:53:53	1.6
@@ -52,11 +52,18 @@
 flags from C<$flags>. These are just the same arguments as given to
 C<DBI->connect>.
 
-The database handle will be cached under the unique id C<$id>. If the same
-id is requested later, the cached handle will be checked (using ping), and
-the connection will be re-established if necessary (be sure to prefix your
-application or module name to the id to make it "more" unique. Things like
-__PACKAGE__ . __LINE__ work fine as well).
+The database handle will be cached under the unique id
+C<$id|$dsn|$user|$pass>. If the same id is requested later, the
+cached handle will be checked (using ping), and the connection will
+be re-established if necessary (be sure to prefix your application or
+module name to the id to make it "more" unique. Things like __PACKAGE__ .
+__LINE__ work fine as well).
+
+The reason C<$id> is necessary is that you might specify special connect
+arguments or special flags, or you might want to configure your $DBH
+differently than maybe other applications requesting the same database
+connection. If none of this is becessary for your application you can
+leave $id empty (i.e. "").
 
 If specified, C<$connect> is a callback (e.g. a coderef) that will be
 called each time a new connection is being established, with the new