openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Dick (JIRA)" <j...@apache.org>
Subject [jira] Commented: (OPENJPA-884) Logging oversight in DB2Dictionary
Date Thu, 05 Feb 2009 15:31:59 GMT

    [ https://issues.apache.org/jira/browse/OPENJPA-884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12670792#action_12670792
] 

Michael Dick commented on OPENJPA-884:
--------------------------------------

I noticed the same thing about history in SVN. This code was added when OpenJPA was in the
incubator. If the incubator's svn repository is still available we could probably find it
there. 

I think I agree with you regarding removing the try / catch. Seems to me if we can't detect
the version of DB2 we'd want to fail early rather than having an empty forUpdateClause. 

Catalina, do you have a recommendation? You've done a lot of work with DB2 and might remember
when this code was added. 

> Logging oversight in DB2Dictionary
> ----------------------------------
>
>                 Key: OPENJPA-884
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-884
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: logging
>    Affects Versions: 1.2.0, 1.2.1, 1.3.0, 2.0.0-M1, 2.0.0
>            Reporter: Milosz Tylenda
>            Assignee: Michael Dick
>            Priority: Trivial
>         Attachments: OPENJPA-884.patch
>
>
> There is a small oversight in DB2Dictionary - there is a check whether TRACE level is
enabled and then an exception is logged on ERROR level.

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


Mime
View raw message