Skip Menu |

This queue is for tickets about the SQL-Statement CPAN distribution.

Report information
The Basics
Id: 61386
Status: resolved
Priority: 0/
Queue: SQL-Statement
People
Owner: Nobody in particular
Requestors: jmv [...] cpan.org
Cc:
AdminCc:
Bug Information
Severity: Important
Broken in: 1.26
Fixed in: (no value)

History Show all quoted text
  Thu Sep 16 02:23:42 2010 jmv [...] cpan.org - Ticket created
Subject: 1.26 + adds table aliases to the sth NAME field
SELECT A.name FROM TABLE A print $sth->{NAME}; In 1.26 and later, yields "A.name" In 1.15 yields "name" I'm guessing this is intentional (allowing SELECT A.name, B.name, etc) but it doesn't really get a callout in the CHANGES file.
  Thu Sep 16 13:37:05 2010 jmv [...] cpan.org - Correspondence added
Show quoted text
> I'm guessing this is intentional (allowing SELECT A.name, B.name, etc) > but it doesn't really get a callout in the CHANGES file.
For my purposes I did the following: my @clean = map { s/^a\.//; $_; } @{$sth->{NAME_lc}}; YMMV.
  Thu Sep 16 13:37:06 2010 jmv [...] cpan.org - Status changed from 'new' to 'open'
  Thu Sep 16 16:46:48 2010 REHSACK [...] cpan.org - Correspondence added
I prove that - in my memory this change came in with 1.27. Thanks for pointing me.
  Sat Jan 15 06:06:20 2011 REHSACK [...] cpan.org - Correspondence added
I'd say this change is made in 1.22 (1.21_1 or 1.21_2). If you write some test code you could do a 'git bisect' or 'svn-bisect' (using App::SVN::Bisect from cpan). From my point of view the current behavior is the correcter one - because SQL::Statement now puts the user specified column names into $sth->{NAME} for all names without wildcards.
  Sat Jan 15 06:06:21 2011 REHSACK [...] cpan.org - Status changed from 'open' to 'resolved'