[ 
https://issues.apache.org/jira/browse/CAY-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15136937#comment-15136937
 ] 

ASF GitHub Bot commented on CAY-2050:
-------------------------------------

GitHub user alexei-grigoriev opened a pull request:

    https://github.com/apache/cayenne/pull/83

    CAY-2050 Refactoring: ParameterBinding to contain ExtendedType proper…

    …ty - switch to new api

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/alexei-grigoriev/cayenne CAY-2050

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cayenne/pull/83.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #83
    
----
commit b7ab8fa9439617c1979cc6496997e900ae769e17
Author: Alexei Grigoriev <agrigor...@objectstyle.com>
Date:   2016-01-27T14:16:49Z

    CAY-2050 Refactoring: ParameterBinding to contain ExtendedType property - 
switch to new api

----


> Refactoring: ParameterBinding to contain ExtendedType property
> --------------------------------------------------------------
>
>                 Key: CAY-2050
>                 URL: https://issues.apache.org/jira/browse/CAY-2050
>             Project: Cayenne
>          Issue Type: Task
>    Affects Versions: 4.0.M3
>            Reporter: Andrus Adamchik
>            Assignee: Andrus Adamchik
>            Priority: Minor
>
> ParameterBinding is a relatively new class. We are not taking full advantage 
> of it through the stack. Here is one enhancement: add ExtendedType property 
> to ParameterBinding class. It is a very logical place for it and would allow 
> us to improve CommonsJdbcEventLogger parameter logging. 
> This may require refactoring of other related methods, such as 
> DbAdapter.bindParameter(..), which will be significantly simplified. So let's 
> do that as well. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to