On Saturday 30 November 2002 23:32, David Wheeler wrote:
(B> On Saturday, November 30, 2002, at 01:57 PM, Ian Barwick wrote:
(B> > Wonderful! Amazing how easy things are to find when you know what
(B> > to search for (I went all through the DBI perlddoc looking for keyword
(B> > like 'case' and 'sensitive'...).
(B> >
(B> > BTW is this a new(ish) feature? I can't find any reference in
(B> > O'Reilly's
(B> > "Programming the Perl DBI", which is a couple of years old.
(B>
(B> Looks like they were added in 1.19, according to the DBI Changes file:
(B>
(B> =head2 Changes in DBI 1.19, 20th July 2001
(B> ...
(B> Added $h->{FetchHashKeyName} = 'NAME_lc' or 'NAME_uc' to alter
(B> behaviour of fetchrow_hashref() method. See docs.
(B
(BAha. Time for me to have another thorough read of the documentation.
(B
(BTalking of which, what's the best way of suggesting changes to
(Bdocumentation? In the DBI doc, FetchHashKeyName is
(Bdescribed thus:
(B
(B `FetchHashKeyName' (string, inherited)
(B This attribute is used to specify which attribute name
(B the fetchrow_hashref() method should use to get the
(B field names for the hash keys. For historical reasons
(B it defaults to '`NAME'' but it is recommended to set
(B it to '`NAME_lc'' or '`NAME_uc'' according to your
(B preference. It can only be set for driver and database
(B tables. For statement handles the value is frozen
(B when prepare() is called.
(B
(BI would suggest something like this:
(B
(B`FetchHashKeyName' (string, inherited)
(B This attribute is used to specify whether the fetchrow_hashref()
(B method should perform case conversion on the field names used for
(B the hash keys. For historical reasons it defaults to '`NAME'' but it is
(B recommended to set it to '`NAME_lc'' (convert to lower case)
(B or '`NAME_uc'' (convert to upper case) according to your
(B preference. It can only be set for driver and database
(B tables. For statement handles the value is frozen
(B when prepare() is called.
(B
(BThanks again,
(B
(BIan Barwick
([EMAIL PROTECTED]
