Bug 45183 - Starting from mysql JDBC connector 5.1.6 a wrong behavior
Summary: Starting from mysql JDBC connector 5.1.6 a wrong behavior
Status: RESOLVED DUPLICATE of bug 43831
Alias: None
Product: Taglibs
Classification: Unclassified
Component: Standard Taglib (show other bugs)
Version: 1.1.0
Hardware: All All
: P2 normal (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
Depends on:
Reported: 2008-06-11 03:43 UTC by Alessandro Polverini
Modified: 2010-10-23 14:20 UTC (History)
1 user (show)


Note You need to log in before you can comment on or make changes to this bug.
Description Alessandro Polverini 2008-06-11 03:43:38 UTC
If using a query with "AS" to rename a column, like here:

<c:set var="sqlBody" value="SELECT c1 as x FROM table"/>
<sql:query var="result" startRow="0" maxRows="3" dataSource="${dataSource}">

the name of the column is "c1" instead of the expected "x".

Detail of the change is specified here:
Comment 1 Henri Yandell 2009-05-25 02:38:53 UTC
JDBC driver specific behaviour afaict.
Comment 2 Alessandro Polverini 2010-10-20 10:14:25 UTC
Mysql developers tells me that they follow the JDBC specs.

Tomcat developers tells me that this is a "driver artifact".

I, as a user, only know that things do not work, application breaks, and an incongruous behavior happens.

Since I provided a complete test case to verify and reproduce the problem I can only link the two bug reports together so you can speak one to another and better understand who has to fix his code.


Thanks for your work,
Comment 3 Jeremy Boynes 2010-10-23 14:20:15 UTC
Fixed in r607683 by using getColumnLabel

Resolving as duplicate. Please reopen if this reoccurs with 1.2

*** This bug has been marked as a duplicate of bug 43831 ***