Author: timbo Date: Wed Jan 26 01:47:32 2005 New Revision: 843 Modified: dbi/trunk/Changes dbi/trunk/DBI.pm Log: Updated docs to clarify that the default fetchrow_hashref behaviour, of returning a ref to a new hash for each row, will not change.
Modified: dbi/trunk/Changes ============================================================================== --- dbi/trunk/Changes (original) +++ dbi/trunk/Changes Wed Jan 26 01:47:32 2005 @@ -31,6 +31,8 @@ Updated docs to recommend some common DSN string attributes. Updated docs for NULL Value placeholders thanks to Brian Campbell. Updated docs for primary_key_info and primary_keys. + Updated docs to clarify that the default fetchrow_hashref behaviour, + of returning a ref to a new hash for each row, will not change. Updated err/errstr/state docs for DBD authors thanks to Steffen Goeldner. Updated handle/attribute docs for DBD authors thanks to Steffen Goeldner. Corrected and updated LongReadLen docs thanks to Bart Lateur. Modified: dbi/trunk/DBI.pm ============================================================================== --- dbi/trunk/DBI.pm (original) +++ dbi/trunk/DBI.pm Wed Jan 26 01:47:32 2005 @@ -5478,9 +5478,11 @@ Because of the extra work C<fetchrow_hashref> and Perl have to perform, it is not as efficient as C<fetchrow_arrayref> or C<fetchrow_array>. -Currently, a new hash reference is returned for each row. I<This will -change> in the future to return the same hash ref each time, so don't -rely on the current behaviour. +By default a reference to a new hash is returned for each row. +It is likely that a future version of the DBI will support an +attribute which will enable the same hash to be reused for each +row. This will give a significant performance boost, but it won't +be enabled by default because of the risk of breaking old code. =item C<fetchall_arrayref>
