Attached is the patch to fix the wrong L<> formatting.
On Thu Jul 18 16:58:50 2013, rurban@x-ray.at wrote:
Show quoted text> blead with svn r15622
>
> t/pod.t ......................... 33/63
> # Failed test 'POD test for blib/lib/DBI/DBD/SqlEngine.pm'
> # at /usr/local/lib/perl5/site_perl/5.18.0/Test/Pod.pm line 186.
> # blib/lib/DBI/DBD/SqlEngine.pm (2090): alternative text
> 'DBD::File/DBD::File::Table' contains non-escaped | or /
>
> # Failed test 'POD test for
> blib/lib/DBI/DBD/SqlEngine/Developers.pod'
> # at /usr/local/lib/perl5/site_perl/5.18.0/Test/Pod.pm line 186.
> # blib/lib/DBI/DBD/SqlEngine/Developers.pod (714): alternative text
> 'DBD::File/DBD::File::Table' contains non-escaped | or /
> # blib/lib/DBI/DBD/SqlEngine/Developers.pod (759): alternative text
> '/DBI::DBD::SqlEngine::DataSource' contains non-escaped | or /
>
> # Failed test 'POD test for blib/lib/DBD/DBM.pm'
> # at /usr/local/lib/perl5/site_perl/5.18.0/Test/Pod.pm line 186.
> # blib/lib/DBD/DBM.pm (652): alternative text 'DBD::File/Metadata'
> contains non-escaped | or /
> # Looks like you failed 3 tests of 63.
> t/pod.t ......................... Dubious, test returned 3 (wstat 768,
> 0x300)
> Failed 3/63 subtests
Index: lib/DBI/DBD/SqlEngine.pm
===================================================================
--- lib/DBI/DBD/SqlEngine.pm (revision 15622)
+++ lib/DBI/DBD/SqlEngine.pm (working copy)
@@ -2091,7 +2091,7 @@
information are in a state which allowes the table's data accessor methods
will be able to fetch/store row information. Implementation details heavily
depends on the table implementation, whereby the most famous is surely
-L<DBD::File/DBD::File::Table|DBD::File::Table>.
+L<DBD::File::Table|DBD::File/"DBD::File::Table">.
=head1 SQL ENGINES
Index: lib/DBI/DBD/SqlEngine/Developers.pod
===================================================================
--- lib/DBI/DBD/SqlEngine/Developers.pod (revision 15622)
+++ lib/DBI/DBD/SqlEngine/Developers.pod (working copy)
@@ -715,7 +715,7 @@
information are in a state which allows the table's data accessor methods
will be able to fetch/store row information. Implementation details heavily
depends on the table implementation, whereby the most famous is surely
-L<DBD::File/DBD::File::Table|DBD::File::Table>.
+L<DBD::File::Table|DBD::File/"DBD::File::Table">.
=head2 DBI::DBD::SqlEngine::Statement
@@ -758,7 +758,7 @@
Returns the table meta data. If there are none for the required table,
a new one is initialized. When after bootstrapping a new I<table_meta>
-and L</DBI::DBD::SqlEngine::DataSource|completing the table name> a
+and L<completing the table name|DBI::DBD::SqlEngine::DataSource> a
mapping can be established between an existing I<table_meta> and the
new bootstrapped one, the already existing is used and a mapping
shortcut between the recent used table name and the already known
Index: lib/DBD/DBM.pm
===================================================================
--- lib/DBD/DBM.pm (revision 15622)
+++ lib/DBD/DBM.pm (working copy)
@@ -650,7 +650,7 @@
});
and other variations on connect() as shown in the L<DBI> docs,
-L<DBD::File/Metadata|DBD::File metadata> and L</Metadata>
+L<DBD::File metadata|DBD::File/"Metadata"> and L</Metadata>
shown below.
Use standard DBI prepare, execute, fetch, placeholders, etc.,
