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

ASF subversion and git services commented on OPENJPA-2820:
----------------------------------------------------------

Commit 049c2ef163d3632f9e91abb91b5ac0d52584d4a9 in openjpa's branch 
refs/heads/master from Romain Manni-Bucau
[ https://gitbox.apache.org/repos/asf?p=openjpa.git;h=049c2ef ]

Merge pull request #71 from eolivelli/fix/OPENJPA-2820-delim

OPENJPA-2820 Track when a DBIdentifier is already delimited in order to save 
memory allocations and cpu

> Track when a DBIdentifier is already delimited in order to save memory 
> allocations and cpu
> ------------------------------------------------------------------------------------------
>
>                 Key: OPENJPA-2820
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-2820
>             Project: OpenJPA
>          Issue Type: Improvement
>          Components: performance
>    Affects Versions: 3.1.3
>            Reporter: Enrico Olivelli
>            Priority: Major
>             Fix For: 3.1.3
>
>
> During the development of [https://github.com/apache/openjpa/pull/69/files] 
> [~rmannibucau] suggested to keep track of the fact that a DBIdentifier 
> contains a name that has been already delimited, this way operations like 
> "removeDelimiters" can be no-op.
>  
> This flag can be set during the creation of a DBIdentifier by the 
> DBDictionary, basically when the DBIdentifier forces delimitAll=true
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to