@@ -16,7 +16,7 @@ use warnings;
1616
1717our ($XS_VERSION , $VERSION );
1818BEGIN {
19- $VERSION = " 1.647 " ; # ==> ALSO update the version in the pod text below!
19+ $VERSION = " 1.648 " ; # ==> ALSO update the version in the pod text below!
2020$XS_VERSION = $VERSION ;
2121$VERSION =~ tr / _// d;
2222}
@@ -148,7 +148,7 @@ sure that your issue isn't related to the driver you're using.
148148
149149=head2 NOTES
150150
151- This is the DBI specification that corresponds to DBI version 1.647
151+ This is the DBI specification that corresponds to DBI version 1.648
152152(see L<DBI::Changes> for details).
153153
154154The DBI is evolving at a steady pace, so it's good to check that
@@ -6899,9 +6899,9 @@ a hash (thanks to H.Merijn Brand):
68996899 print "$row{region}: $row{sales}\n";
69006900 }
69016901
6902- but has a small drawback: If data already fetched call to L</bind_columns>
6903- will flush current values. If you want to bind_columns after you have fetched
6904- you can use:
6902+ but has a small drawback: If the data has already been fetched, the call to
6903+ L</bind_columns> will flush current values. If you want to bind_columns after
6904+ you have fetched, you can use:
69056905
69066906 use feature "refaliasing";
69076907 no warnings "experimental::refaliasing";
@@ -6914,7 +6914,7 @@ or, with older perl versions:
69146914 use Data::Alias;
69156915 alias @$data{ $sth->{NAME_lc}->@* } = @$row;
69166916
6917- This is useful in situations when you have many left joins, but wanna to join
6917+ This is useful in situations when you have many left joins, but want to join
69186918your %$data hash to only subset of fetched values.
69196919
69206920=head3 C<dump_results >
0 commit comments