Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:38289
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.200.172 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:mime-version:content-type;
        b=Rl5K6vBg3ZIrEYIZbE77piiIDTejJyfS7RJZjUfksPMPX687G/mDHCgmjkUNaT0IYr
         ZgJejQqfFPDqajchDd2CQjXWxBpcJKWcrYTDFCuXjicSLPFMJWZNTPbSOrAM9JXXF1E2
         XcREchhpaBsFiiLBosXJt/cBKKgpA8/c6ds3w=
Message-ID: <cb13bf640806161016x5678f7adq520bb75b7e1b79f9@mail.gmail.com>
Date: Mon, 16 Jun 2008 11:16:21 -0600
To: internals@lists.php.net
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_7706_27339844.1213636581322"
Subject: case folding array string keys
From: davelee.com@gmail.com ("Dave Lee")

------=_Part_7706_27339844.1213636581322
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi,
I have a patch that I'm hoping might be useful to PHP developers, at least
those using PostgreSQL. The patch provides case folding of string keys
during hash lookups. The need for this comes from ...

We're transitioning from MySQL to PostgreSQL, and like many, we use camel
casing for naming tables and columns in our db. In PostgreSQL, (unquoted)
table and column names are case folded to lower case, so where we currently
have $row['someForeignId'], we would need to rewrite the key to
'someforeignid'. Besides being a lesson that we should use _ naming in the
future, it was clear there was no quick solution, we'd be forced to modify
many lines of code, and possibly end up with less readability. Instead, I
added a caseFold flag to the HashTable struct, which is later checked
in zend_hash_find() where, if configured, case folding of the key is
performed before hash lookup.

My question to the list is, can this functionality be added in a way that
doesn't adversely effect developers who won't use it, but helps us
PostgreSQL users and anyone else who might find it useful?  Judging from my
searches on the subject, it's not an uncommon impedance for PHP/PostgreSQL
users.

thanks,
Dave

------=_Part_7706_27339844.1213636581322--