commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Fabulich (JIRA)" <>
Subject [jira] Commented: (DBUTILS-34) BasicRowProcessor loses any information on database field case
Date Wed, 11 Feb 2009 08:10:59 GMT


Dan Fabulich commented on DBUTILS-34:

Liam helped me understand the point of this on the commons-dev list.  Checked into "bugfixing"
branch in revision 743269.

CaseInsensitiveHashMap ISN'T thread-safe, but then, neither is HashMap!  So, uh, never mind.

> BasicRowProcessor loses any information on database field case
> --------------------------------------------------------------
>                 Key: DBUTILS-34
>                 URL:
>             Project: Commons DbUtils
>          Issue Type: Improvement
>    Affects Versions: 1.0
>            Reporter: Fabio Insaccanebbia
>            Priority: Minor
>         Attachments:, 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
> 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

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

View raw message