@@ -16,7 +16,7 @@ use warnings;
16
16
17
17
our ($XS_VERSION , $VERSION );
18
18
BEGIN {
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!
20
20
$XS_VERSION = $VERSION ;
21
21
$VERSION =~ tr / _// d;
22
22
}
@@ -148,7 +148,7 @@ sure that your issue isn't related to the driver you're using.
148
148
149
149
=head2 NOTES
150
150
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
152
152
(see L<DBI::Changes> for details).
153
153
154
154
The 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):
6899
6899
print "$row{region}: $row{sales}\n";
6900
6900
}
6901
6901
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:
6905
6905
6906
6906
use feature "refaliasing";
6907
6907
no warnings "experimental::refaliasing";
@@ -6914,7 +6914,7 @@ or, with older perl versions:
6914
6914
use Data::Alias;
6915
6915
alias @$data{ $sth->{NAME_lc}->@* } = @$row;
6916
6916
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
6918
6918
your %$data hash to only subset of fetched values.
6919
6919
6920
6920
=head3 C<dump_results >
0 commit comments