On Tue, Aug 11, 2009 at 01:21:53PM -0400, Link McGaughey wrote:
> 
> [...] I too am using the
> fetchrow_hashref, however it drops the table prefix on the return
> column names, which in turn clobbers column names that are the same
> across tables.  Thus the reason for this thread.
> 
> I was really just looking for any future planning done on the DBI side
> of things to aid with getting back full information.  Either a flag to
> pass into the function call, or new functions which return the table
> names prefixed as you would see when running the SQL directly from a
> console.  It seems that other languages, such as Java, do not seem to
> have is issue, both ways of retrieval are possible.  If the
> fetchrow_hashref were changed to house both types of keys (those
> without table prefixes and those with), in the way Java and other
> languages work, then this would be a mute point.

I know that a few _databases_ can do that, but most don't. For those
that don't, the client API (in Java or any other language) simply can't
provide the information.

For those that do the corresponding DBI driver could provide a
driver-private attribute to enable table name/aliases in the
hash keys.

Tim.

Reply via email to