Not to speak for Tim on this but here is my 2cents worth,
Your case here is poor SQL and or table design which you are trying to
account for with DBI.
If you intend to use the cursor/recordset column 'headers' as unique
identifiers then you should set them up as such.
ie
Select test.id as user_name,
new.id as user_id,
test.name as old_name,
new.number as Number
from test, new
where test.id=new.id
Never assume your third party tool will will fix this sort of problem
for you.
cheers
Tim Bunce wrote:
----- Forwarded message from Link McGaughey <[email protected]> -----
Date: Wed, 5 Aug 2009 18:41:56 -0400
Subject: Question regarding DBI status
From: Link McGaughey <[email protected]>
To: [email protected]
Tim,
I found your information from CPAN, and had a question regarding the
status of active development for DBI more specifically
'fetchrow_hashref'.
The issue that I am having is based around 'JOIN' statements and table
with same named columns.
I have found several work arounds to my problem, but didn't know if
there was a version of DBI that left the table name prefixed to the
column name. (ie table.column).
Any information would be great.
Thanks,
-Link
----- End forwarded message -----