Author: timbo
Date: Thu Dec 16 08:49:10 2004
New Revision: 633
Modified:
dbi/trunk/DBI.pm
dbi/trunk/lib/DBD/DBM.pm
dbi/trunk/lib/DBD/File.pm
dbi/trunk/lib/DBD/Proxy.pm
dbi/trunk/lib/DBD/Sponge.pm
dbi/trunk/lib/DBI/Const/GetInfo/ANSI.pm
dbi/trunk/lib/DBI/Const/GetInfo/ODBC.pm
dbi/trunk/lib/DBI/Const/GetInfoReturn.pm
dbi/trunk/lib/DBI/Const/GetInfoType.pm
dbi/trunk/lib/DBI/ProfileDumper.pm
dbi/trunk/lib/DBI/ProxyServer.pm
dbi/trunk/lib/DBI/PurePerl.pm
Log:
Thanks to podchecker. (Not 100% clean, but much closer.)
Modified: dbi/trunk/DBI.pm
==============================================================================
--- dbi/trunk/DBI.pm (original)
+++ dbi/trunk/DBI.pm Thu Dec 16 08:49:10 2004
@@ -2290,7 +2290,7 @@
UPDATE people SET age = ? WHERE name = ?
});
$sth->execute(undef, "Joe Bloggs");
-
+
However, care must be taken in the particular case of trying to use
NULL values to qualify a C<WHERE> clause. Consider:
@@ -2336,7 +2336,7 @@
4) age = ? OR (age IS NULL AND ? IS NULL)
5) age = ? OR (age IS NULL AND SP_ISNULL(?) = 1)
6) age = ? OR (age IS NULL AND ? = 1)
-
+
Statements formed with the above C<WHERE> clauses require execute
statements as follows:
@@ -3975,16 +3975,16 @@
=over 4
-B<0>: A warning will be generated, and finish() will be called on
+=item B<0>: A warning will be generated, and finish() will be called on
the statement handle before it is returned. This is the default
behaviour if $if_active is not passed.
-B<1>: finish() will be called on the statement handle, but the
+=item B<1>: finish() will be called on the statement handle, but the
warning is suppressed.
-B<2>: Disables any checking.
+=item B<2>: Disables any checking.
-B<3>: The existing active statement handle will be removed from the
+=item B<3>: The existing active statement handle will be removed from the
cache and a new statement handle prepared and cached in its place.
This is the safest option because it doesn't affect the state of the
old handle, it just removes it from the cache. [Added in DBI 1.40]
Modified: dbi/trunk/lib/DBD/DBM.pm
==============================================================================
--- dbi/trunk/lib/DBD/DBM.pm (original)
+++ dbi/trunk/lib/DBD/DBM.pm Thu Dec 16 08:49:10 2004
@@ -710,7 +710,7 @@
DBD::DBM operates like all other DBD drivers - it's basic syntax and operation
is specified by DBI. If you're not familiar with DBI, you should start by
reading L<DBI> and the documents it points to and then come back and read this
file. If you are familiar with DBI, you already know most of what you need to
know to operate this module. Just jump in and create a test script something
like the one shown below.
-You should be aware that there are several options for the SQL engine
underlying DBD::DBM, see L<Supported SQL>. There are also many options for DBM
support, see especially the section on L<Adding multi-column support with
MLDBM>.
+You should be aware that there are several options for the SQL engine
underlying DBD::DBM, see L<Supported SQL syntax>. There are also many options
for DBM support, see especially the section on L<Adding multi-column support
with MLDBM>.
But here's a sample to get you started.
@@ -858,7 +858,7 @@
SDBM_File, the default file type is quite limited, so if you are going to use
MLDBM, you should probably use a different type, see L<AnyDBM_File>.
-See below for some L<Gotchas and Warnings> about MLDBM.
+See below for some L<GOTCHAS AND WARNINGS> about MLDBM.
=head2 Support for Berkeley DB
Modified: dbi/trunk/lib/DBD/File.pm
==============================================================================
--- dbi/trunk/lib/DBD/File.pm (original)
+++ dbi/trunk/lib/DBD/File.pm Thu Dec 16 08:49:10 2004
@@ -659,8 +659,8 @@
INI files. The module is based on the SQL::Statement module, a simple
SQL engine.
-See L<DBI(3)> for details on DBI, L<SQL::Statement(3)> for details on
-SQL::Statement and L<DBD::CSV(3)> or L<DBD::IniFile(3)> for example
+See L<DBI> for details on DBI, L<SQL::Statement> for details on
+SQL::Statement and L<DBD::CSV> or L<DBD::IniFile> for example
drivers.
@@ -755,8 +755,7 @@
my(@list) = $dbh->func('list_tables');
Note that the list includes all files contained in the directory, even
-those that have non-valid table names, from the view of SQL. See
-L<Creating and dropping tables> above.
+those that have non-valid table names, from the view of SQL.
=back
@@ -792,7 +791,7 @@
=head1 SEE ALSO
-L<DBI(3)>, L<Text::CSV_XS(3)>, L<SQL::Statement(3)>
+L<DBI>, L<Text::CSV_XS>, L<SQL::Statement>
=cut
Modified: dbi/trunk/lib/DBD/Proxy.pm
==============================================================================
--- dbi/trunk/lib/DBD/Proxy.pm (original)
+++ dbi/trunk/lib/DBD/Proxy.pm Thu Dec 16 08:49:10 2004
@@ -715,7 +715,7 @@
Before connecting to a remote database, you must ensure, that a Proxy
server is running on the remote machine. There's no default port, so
you have to ask your system administrator for the port number. See
-L<DBI::ProxyServer(3)> for details.
+L<DBI::ProxyServer> for details.
Say, your Proxy server is running on machine "alpha", port 3334, and
you'd like to connect to an ODBC database called "mydb" as user "joe"
@@ -732,7 +732,7 @@
connection to the Proxy server on "alpha" which in turn will connect
to the ODBC database.
-Refer to the L<DBI(3)> documentation on the C<connect> method for a way
+Refer to the L<DBI> documentation on the C<connect> method for a way
to automatically use DBD::Proxy without having to change your code.
DBD::Proxy's DSN string has the format
@@ -782,7 +782,7 @@
$cipherRef = $class->new(pack("H*", $key));
and pass this object to the RPC::PlClient module when creating a
-client. See L<RPC::PlClient(3)>. Example:
+client. See L<RPC::PlClient>. Example:
cipher=IDEA;key=97cd2375efa329aceef2098babdc9721
@@ -794,7 +794,7 @@
The usercipher/userkey secret is B<your> private secret.
Of course encryption requires an appropriately configured server. See
-<DBD::ProxyServer(3)/CONFIGURATION FILE>.
+<DBD::ProxyServer/CONFIGURATION FILE>.
=item debug
@@ -841,7 +841,7 @@
This attribute can be used to reduce network traffic: By default calls
to $dbh->quote() are passed to the remote driver. Of course this slows
down things quite a lot, but is the safest default behaviour.
-
+
However, if you set the I<proxy_quote> attribute to the value 'C<local>'
either in the database handle or in the statement handle, and the call
to quote has only one parameter, then the local default DBI quote
@@ -871,13 +871,13 @@
=over
-=item 1.)
-
+=item 1
+
The first step is fetching the value of the key "csv_tables" in the
handle $dbh. The value returned is complex, a hash ref.
-
-=item 2.)
-
+
+=item 2
+
The second step is storing some value (the right hand side of the
assignment) as the key "passwd" in the hash ref from step 1.
@@ -921,6 +921,6 @@
=head1 SEE ALSO
-L<DBI(3)>, L<RPC::PlClient(3)>, L<Storable(3)>
+L<DBI>, L<RPC::PlClient>, L<Storable>
=cut
Modified: dbi/trunk/lib/DBD/Sponge.pm
==============================================================================
--- dbi/trunk/lib/DBD/Sponge.pm (original)
+++ dbi/trunk/lib/DBD/Sponge.pm Thu Dec 16 08:49:10 2004
@@ -253,7 +253,7 @@
=over 4
-=item o
+=item *
The C<$statement> here is an arbitrary statement or name you want
to provide as identity of your data. If you're using DBI::Profile
@@ -262,16 +262,16 @@
Generally it's expected that you are preparing a statement handle
as if a C<select> statement happened.
-=item o
+=item *
C<$data> is a reference to the data you are providing, given as an array of
arrays.
-=item o
+=item *
C<$names> is a reference an array of column names for the C<$data> you are
providing.
The number and order should match the number and ordering of the C<$data>
columns.
-=item o
+=item *
C<%attr> is a hash of other standard DBI attributes that you might pass to a
prepare statement.
@@ -295,6 +295,6 @@
=head1 SEE ALSO
-L<DBI(3)>
+L<DBI>
=cut
Modified: dbi/trunk/lib/DBI/Const/GetInfo/ANSI.pm
==============================================================================
--- dbi/trunk/lib/DBI/Const/GetInfo/ANSI.pm (original)
+++ dbi/trunk/lib/DBI/Const/GetInfo/ANSI.pm Thu Dec 16 08:49:10 2004
@@ -12,7 +12,7 @@
=head1 NAME
- DBI::Const::GetInfo::ANSI - ISO/IEC SQL/CLI Constants for GetInfo
+DBI::Const::GetInfo::ANSI - ISO/IEC SQL/CLI Constants for GetInfo
=head1 SYNOPSIS
Modified: dbi/trunk/lib/DBI/Const/GetInfo/ODBC.pm
==============================================================================
--- dbi/trunk/lib/DBI/Const/GetInfo/ODBC.pm (original)
+++ dbi/trunk/lib/DBI/Const/GetInfo/ODBC.pm Thu Dec 16 08:49:10 2004
@@ -12,7 +12,7 @@
=head1 NAME
- DBI::Const::GetInfo::ODBC - ODBC Constants for GetInfo
+DBI::Const::GetInfo::ODBC - ODBC Constants for GetInfo
=head1 SYNOPSIS
Modified: dbi/trunk/lib/DBI/Const/GetInfoReturn.pm
==============================================================================
--- dbi/trunk/lib/DBI/Const/GetInfoReturn.pm (original)
+++ dbi/trunk/lib/DBI/Const/GetInfoReturn.pm Thu Dec 16 08:49:10 2004
@@ -23,7 +23,7 @@
=head1 NAME
- DBI::Const::GetInfoReturn - Data and functions for describing GetInfo results
+DBI::Const::GetInfoReturn - Data and functions for describing GetInfo results
=head1 SYNOPSIS
Modified: dbi/trunk/lib/DBI/Const/GetInfoType.pm
==============================================================================
--- dbi/trunk/lib/DBI/Const/GetInfoType.pm (original)
+++ dbi/trunk/lib/DBI/Const/GetInfoType.pm Thu Dec 16 08:49:10 2004
@@ -23,7 +23,7 @@
=head1 NAME
- DBI::Const::GetInfoType - Data describing GetInfo type codes
+DBI::Const::GetInfoType - Data describing GetInfo type codes
=head1 SYNOPSIS
Modified: dbi/trunk/lib/DBI/ProfileDumper.pm
==============================================================================
--- dbi/trunk/lib/DBI/ProfileDumper.pm (original)
+++ dbi/trunk/lib/DBI/ProfileDumper.pm Thu Dec 16 08:49:10 2004
@@ -65,7 +65,7 @@
File => 'dbi.prof' );
The C<Path> option takes the same values as in
-L<DBI::Profile|DBI:Profile>. The C<File> option gives the name of the
+L<DBI::Profile>. The C<File> option gives the name of the
file where results will be collected. If it already exists it will be
overwritten.
@@ -107,7 +107,7 @@
DBI::ProfileDumper 1.0
Path = [ DBIprofile_Statement, DBIprofile_MethodName ]
Program = t/42profile_data.t
-
+
+ 1 SELECT name FROM users WHERE id = ?
+ 2 prepare
= 1 0.0312958955764771 0.000490069389343262 0.000176072120666504
0.00140702724456787 1023115819.83019 1023115819.86576
Modified: dbi/trunk/lib/DBI/ProxyServer.pm
==============================================================================
--- dbi/trunk/lib/DBI/ProxyServer.pm (original)
+++ dbi/trunk/lib/DBI/ProxyServer.pm Thu Dec 16 08:49:10 2004
@@ -375,13 +375,11 @@
DBI::ProxyServer - a server for the DBD::Proxy driver
-
=head1 SYNOPSIS
use DBI::ProxyServer;
DBI::ProxyServer::main(@ARGV);
-
=head1 DESCRIPTION
DBI::Proxy Server is a module for implementing a proxy for the DBI proxy
@@ -402,7 +400,7 @@
execute and restrict access to those. (Requires a DBI driver that supports
parameter binding.) See L</CONFIGURATION FILE>.
-The provided driver script, L<dbiproxy(1)>, may either be used as it is or
+The provided driver script, L<dbiproxy>, may either be used as it is or
used as the basis for a local version modified to meet your needs.
=head1 OPTIONS
@@ -413,7 +411,7 @@
The ProxyServer inherits all of RPC::PlServer's and hence Net::Daemon's
options and option handling, in particular the ability to read
options from either the command line or a config file. See
-L<RPC::PlServer(3)>. See L<Net::Daemon(3)>. Available options include
+L<RPC::PlServer>. See L<Net::Daemon>. Available options include
=over 4
@@ -449,8 +447,7 @@
An array ref with a list of clients. Clients are hash refs, the attributes
I<accept> (0 for denying access and 1 for permitting) and I<mask>, a Perl
-regular expression for the clients IP number or its host name. See
-L<"Access control"> below.
+regular expression for the clients IP number or its host name.
=item I<configfile> (B<--configfile=file>)
@@ -466,7 +463,7 @@
=item I<facility> (B<--facility=mode>)
-(UNIX only) Facility to use for L<Sys::Syslog (3)>. The default is
+(UNIX only) Facility to use for L<Sys::Syslog>. The default is
B<daemon>.
=item I<group> (B<--group=gid>)
@@ -494,7 +491,7 @@
Be default logging messages will be written to the syslog (Unix) or
to the event log (Windows NT). On other operating systems you need to
specify a log file. The special value "STDERR" forces logging to
-stderr. See L<Net::Daemon::Log(3)> for details.
+stderr. See L<Net::Daemon::Log> for details.
=item I<mode> (B<--mode=modename>)
@@ -625,7 +622,7 @@
# the most specialized rules for single machines/users are 1st
# then the denying rules
# the the rules about whole networks
-
+
# rule: internal_webserver
# desc: to get statistical information
{
@@ -643,7 +640,7 @@
statistic_area => 'select count(*) from
e01admin.e01e203 where geb_bezei like ?',
}
},
-
+
# rule: internal_bad_guy_1
{
mask => '^10\.95\.81\.1$',
@@ -885,6 +882,6 @@
=head1 SEE ALSO
-L<dbiproxy(1)>, L<DBD::Proxy(3)>, L<DBI(3)>, L<RPC::PlServer(3)>,
-L<RPC::PlClient(3)>, L<Net::Daemon(3)>, L<Net::Daemon::Log(3)>,
-L<Sys::Syslog(3)>, L<Win32::EventLog(3)>, L<syslog(2)>
+L<dbiproxy>, L<DBD::Proxy>, L<DBI>, L<RPC::PlServer>,
+L<RPC::PlClient>, L<Net::Daemon>, L<Net::Daemon::Log>,
+L<Sys::Syslog>, L<Win32::EventLog>, L<syslog>
Modified: dbi/trunk/lib/DBI/PurePerl.pm
==============================================================================
--- dbi/trunk/lib/DBI/PurePerl.pm (original)
+++ dbi/trunk/lib/DBI/PurePerl.pm Thu Dec 16 08:49:10 2004
@@ -848,7 +848,7 @@
=head1 NAME
- DBI::PurePerl -- a DBI emulation using pure perl (no C/XS compilation
required)
+DBI::PurePerl -- a DBI emulation using pure perl (no C/XS compilation required)
=head1 SYNOPSIS
@@ -947,7 +947,7 @@
environment variable as usual. But to enable individual handle
tracing using the trace() method you also need to set the DBI_TRACE
environment variable, but set it to 0.
-
+
=head2 Parameter Usage Checking
The DBI does some basic parameter count checking on method calls.
