You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2015/09/05 13:33:45 UTC
[jira] [Commented] (OPENJPA-2602) OracleDictionary uses reflection
way too often
[ https://issues.apache.org/jira/browse/OPENJPA-2602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14731938#comment-14731938 ]
ASF subversion and git services commented on OPENJPA-2602:
----------------------------------------------------------
Commit 1701372 from [~struberg] in branch 'openjpa/trunk'
[ https://svn.apache.org/r1701372 ]
OPENJPA-2602 replace ongoing Class.forName with 1x lookup to improve performance and minimize locks
> OracleDictionary uses reflection way too often
> ----------------------------------------------
>
> Key: OPENJPA-2602
> URL: https://issues.apache.org/jira/browse/OPENJPA-2602
> Project: OpenJPA
> Issue Type: Improvement
> Components: jdbc
> Affects Versions: 2.4.0
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Fix For: 2.4.1
>
> Attachments: OPENJPA-2602.4review.2.patch
>
>
> OracleDictionary has many Class.forName, getMethod and getField for oracle.jdbc.OraclePreparedStatement.
> This gets executed every time a setString gets used. Which can create quite some overhead.
> We might check those Members at construction time and use this info later at runtime.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)