Bug #56475 for SQL-Statement: [PATCH] Fix spelling errors

Hi, the attached patch was introduced in Debian to fix several spelling errors in the documentation. Please consider applying it in the next release. Regards, Ansgar

Description: fix POD spelling Author: Jonathan Yu <jawnsy@cpan.org> Origin: vendor Forwarded: no --- libsql-statement-perl.orig/lib/SQL/Parser.pm +++ libsql-statement-perl/lib/SQL/Parser.pm @@ -3117,7 +3117,7 @@ =head1 Subclassing SQL::Parser In the event you need to either extend or modify SQL::Parser's -default behavior, the following methods may be overriden +default behavior, the following methods may be overridden to modify the behavior: =over @@ -3146,7 +3146,7 @@ =head1 The parse structure This section outlines the B<now-deprecated> hash interface to the parsed -structure. It is included B<for backwards compatability only>. You should +structure. It is included B<for backwards compatibility only>. You should use the SQL::Statement object interface to the structure instead. See L<SQL::Statement>. B<Parse Structures> --- libsql-statement-perl.orig/lib/SQL/Statement.pm +++ libsql-statement-perl/lib/SQL/Statement.pm @@ -2139,7 +2139,7 @@ SQL::Statement is a small embeddable Database Management System (DBMS), this means that it provides all of the services of a simple DBMS except that -instead of a persistant storage mechanism, it has two things: 1) an in-memory +instead of a persistent storage mechanism, it has two things: 1) an in-memory storage mechanism that allows you to prepare, execute, and fetch from SQL statements using temporary tables and 2) a set of software sockets where any author can plug in any storage mechanism. @@ -2152,7 +2152,7 @@ =head1 INSTALLATION There are no prerequisites for using this as a standalone parser. If you want -to access persistant stored data, you either need to write a subclass or use +to access persistent stored data, you either need to write a subclass or use one of the DBI DBD drivers. You can install this module using CPAN.pm, CPANPLUS.pm, PPM, apt-get, or other packaging tools. Or you can download the tar.gz file form CPAN and use the standard perl mantra: @@ -2313,7 +2313,7 @@ only. To get patches for earlier versions, you need to get an agreement with a developer of your choice - who might or might not report the issue and a suggested fix upstream (depends on -the license you've choosen). +the license you've chosen). =head2 Business support and maintenance --- libsql-statement-perl.orig/lib/SQL/Statement/Embed.pod +++ libsql-statement-perl/lib/SQL/Statement/Embed.pod @@ -22,7 +22,7 @@ Consider what needs to happen to perform a SELECT query on our 'Foo' data: - * recieve a SQL string + * receive a SQL string * parse the SQL string into a request structure * open the table(s) specified in the request * define column names and postions for the table @@ -230,4 +230,4 @@ This document may be freely modified and distributed under the same terms as Perl itself. -=cut \ No newline at end of file +=cut --- libsql-statement-perl.orig/lib/SQL/Statement/Functions.pm +++ libsql-statement-perl/lib/SQL/Statement/Functions.pm @@ -94,7 +94,7 @@ sprintf "%02s::%02s::%02s",(localtime)[2,1,0] } -More complex functions can make use of a number of arguments always passed to functions automatically. Functions always recieve these values in @_: +More complex functions can make use of a number of arguments always passed to functions automatically. Functions always receive these values in @_: sub FOO { my($self,$sth,$rowhash,@params); --- libsql-statement-perl.orig/lib/SQL/Statement/Structure.pod +++ libsql-statement-perl/lib/SQL/Statement/Structure.pod @@ -149,7 +149,7 @@ This would return two instances of C<SQL::Statement::Param>. Param objects implement a single method, C<$param->num()>, which retrieves the parameter -number. (0 and 1, in the above example). As of now, not very usefull ... :-) +number. (0 and 1, in the above example). As of now, not very useful ... :-) =head2 B<row_values> @@ -304,7 +304,7 @@ =head2 execute When called from a DBD or other subclass of SQL::Statement, the execute() -method will be executed against whatever datasource (persistant storage) is +method will be executed against whatever datasource (persistent storage) is supplied by the DBD or the subclass (e.g. CSV files for L<DBD::CSV>, or BerkeleyDB for L<DBD::DBM>). If you are using L<SQL::Statement> directly rather than as a subclass, you can call the execute() method and the