[ 
https://issues.apache.org/jira/browse/DBUTILS-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henri Yandell closed DBUTILS-34.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 1.2

svn ci -m "Merging in Dab Fabulich's work on 
https://svn.apache.org/repos/asf/commons/sandbox/dbutils/bugfixing from 
-r741987:747723. Resolving DBUTILS-34 - DBUTILS-37 - DBUTILS-29 - DBUTILS-14 - 
DBUTILS-31 - DBUTILS-39 - DBUTILS-41 - DBUTILS-44 - DBUTILS-33 - DBUTILS-42 - 
DBUTILS-40"  

Sending        pom.xml
Sending        src/java/org/apache/commons/dbutils/BasicRowProcessor.java
Sending        src/java/org/apache/commons/dbutils/BeanProcessor.java
Sending        src/java/org/apache/commons/dbutils/QueryRunner.java
Adding         
src/java/org/apache/commons/dbutils/handlers/AbstractListHandler.java
Sending        
src/java/org/apache/commons/dbutils/handlers/ArrayListHandler.java
Sending        src/java/org/apache/commons/dbutils/handlers/BeanListHandler.java
Sending        
src/java/org/apache/commons/dbutils/handlers/ColumnListHandler.java
Deleting       
src/java/org/apache/commons/dbutils/handlers/GenericListHandler.java
Sending        src/java/org/apache/commons/dbutils/handlers/MapListHandler.java
Sending        src/test/org/apache/commons/dbutils/BaseTestCase.java
Adding         src/test/org/apache/commons/dbutils/QueryRunnerTest.java
Transmitting file data .........
Committed revision 747724.

> BasicRowProcessor loses any information on database field case
> --------------------------------------------------------------
>
>                 Key: DBUTILS-34
>                 URL: https://issues.apache.org/jira/browse/DBUTILS-34
>             Project: Commons DbUtils
>          Issue Type: Improvement
>    Affects Versions: 1.0
>            Reporter: Fabio Insaccanebbia
>            Priority: Minor
>             Fix For: 1.2
>
>         Attachments: BasicRowProcessor.java, BasicRowProcessor.patch
>
>
> In the BasicRowProcessor class there is a comment about the toMap method:
> " This  implementation returns a <code>Map</code> with case insensitive 
> column names as keys.  Calls to map.get("COL") and map.get("col") return the 
> same value"
> So the "contract" of this method just says that the "get" method is case 
> insensitive. The current implementation obtains this result by putting all 
> the keys in lowercase. This way we simply "lose" every information about the 
> case of the fields. If you call the "keys" iterator, you don't have anymore 
> the keys you inserted, but the "lowercase" version. 
> I find it not completely correct: I would expect the keys to be exactly the 
> ones I set on the database, also if I can get the value in a case insensitive 
> way.
> I still have to find the idea for a pathc, but I'd like to know if you find 
> my reasoning correct.
> I consider the current behaviour a problem, since I had to map the database 
> fields to a bean and the "case" made it impossible, even if I had set my 
> database to return mixed case fieldnames.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to