You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Carl Hall (JIRA)" <ji...@apache.org> on 2014/11/20 23:39:33 UTC
[jira] [Updated] (DBUTILS-121) Allow influencing the setter method
used
[ https://issues.apache.org/jira/browse/DBUTILS-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carl Hall updated DBUTILS-121:
------------------------------
Attachment: dbutils-121.patch
Attaching a patch for this.
> Allow influencing the setter method used
> ----------------------------------------
>
> Key: DBUTILS-121
> URL: https://issues.apache.org/jira/browse/DBUTILS-121
> Project: Commons DbUtils
> Issue Type: Bug
> Affects Versions: 1.6
> Reporter: Carl Hall
> Attachments: dbutils-121.patch
>
>
> I have cases where the field in a bean doesn't quite match the column it is stored as. e.g. {{Timestamp}} in the database but {{org.joda.DateTime}} in the bean. It would be nice to allow the bean processor to have influence over which setter method is used, so that a setter can take a parameter that's the type of the database column but convert it to the internally stored type.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)