I wouldn't want people to go away from this question thinking I'm still sulking about it and saying that DBI is broken in some way, I'm really not. I found my own workaround and you guys have very helpfully shown me that other way to go about it, the "as x" thing.
Maybe it's because I'm relatively new to this stuff that I even asked, but I want to repeat my point as simply as possible.
I selected "a.id" and "b.id" from some tables. I assumed that because I'd selected them using those names, that DBI would put them into the hash with those names.
I wasn't enraged or even mildly surprised that it didn't. I just wondered why not.
Are there any negative consequences that I can't see, that would occur if DBI did it "my" way?
($_='kkvvttuubbooppuuiiffssqqffssmmiibbddllffss') =~y~b-v~a-z~s; print
In reply to Re: 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: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |