I think my point is in direct contradiction of 'this is expected behaviour' though -- my post was pretty much about the fact that I didn't expect it!
What you're saying is, this is not a feature request I should make, or some lesser-known option in DBD::MySQL like for instance --
use_table_prefixes => 1
-- it's a feature. I guess I can live with that.
But I still think it's kind of intuitive that, having already distinguished between the fields in order to get the select to work, I shouldn't have to do it twice to get the hashref to work. In what circumstances would my expected behaviour have negative consequences?
($_='kkvvttuubbooppuuiiffssqqffssmmiibbddllffss') =~y~b-v~a-z~s; print
In reply to Re: Hash-clobbering in DBD's fetchrow_hashref
by Cody Pendant
in thread Hash-clobbering in DBD's fetchrow_hashref
by Cody Pendant
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |