Question on FetchHashKeyName

Hello All,

I have been using DBI for some years with MySQL, PostgreSQL, SQLite and Oracle. When using DBI with Oracle I always set FetchHashKeyName to NAME_lc.

Over the weekend I was prototyping a new system and I wanted to use SQLite since I was somewhat offline. All of the hash keys were lower-case by default, but the protocol I was trying to adhere to was using camelCase.

So my question is (and is has possibly been responded to before):

- Would it be possible to have FetchHashKeyName preserve case? so if a database was using camelCase this would be preserved.

Our basis datamodel is encapsulated in views for separate service/application/protocol implementations, so if I would get the views to adhere to the protocol, I would not have to translated the hash keys (and maintain the translation dictionary afterwards.

I checked some FAQ without luck (https://www.fnal.gov/docs/products/perl/pod/site_perl/DBI/FAQ.html), which however seem a bit obsolete (last update 1997) and I cannot find any trace of the FAQ on MetaCPAN.

jonasbn
—
pauseid: JONASBN
email: [email protected]
twitter: @jonasbn
blog: https://lastmover.wordpress.com/

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJYtcNgAAoJELBdKQZWcKdtDPEQAK99jyShhM48QT86IBUzht/b
PimWc7/ci47xr8MNcfTrHn0X9R8Qv7slraSuxLMx3U9R00FYzQOuhNR/BVhhNMi4
wUgVUH++XNMuMsxmml2dmn0jU2ic++lRl7QXiBIxFTrie7mN9KcPAuxOwNjclqGi
eEf0NGBI+Uv2v42rWA35MpSdNMDCi3n+KJmVFODv3eqkDWxWLixkziEHwfATmL8V
89Co4ZbAOpT/yp0puNG2t/pF4tZvgrLX2ydGOQRro1PeXeZLo0IrbPH7wEjZMo/F
Gf4r0Ta0EJGk8lmVN3NxAIvPyjrB2EbKutg3y5TolyuoDQgunlSeX6YbvrIKV6Zn
E1rtoNJ/pT2k3oobltiWTRQNajpy48j4AgBWNlouUOG6uitZngLomQTRW7HObFxf
xPL8uV6FGHCh4v66xOgQa4xv6KxjYEc/NUv68nb8UTvzZPo1Ms/TAPqXJMtenuOe
H5em8FN0kbg5jQw1BPvybR/FLvT5nW31X2GJ6IKOuHLxF/7KPBUhzcaW5l1MxRvh
WqQklt81BRLJQHSHOEGF0H2h3YJ/c2OByxDsPF9etCMdHaR63b78fV0c0xBU0eaZ
SCXq9H2RAnfz9FYaUKu0F+G7PWHNiCoS57KA4p2Z6G3R/odwcBQvwqtANKdWgiyj
h/5VH8dFvYQ9Tqj/cypN
=Lhlg
-----END PGP SIGNATURE-----