[
https://issues.apache.org/jira/browse/SYNCOPE-634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14314334#comment-14314334
]
ASF subversion and git services commented on SYNCOPE-634:
---------------------------------------------------------
Commit 75902df94df9cc6c9f1bb51280b258b69c89bcc1 in syncope's branch
refs/heads/2_0_X from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=75902df ]
[SYNCOPE-620] Merge for SYNCOPE-634
> performance optimization for content loading
> --------------------------------------------
>
> Key: SYNCOPE-634
> URL: https://issues.apache.org/jira/browse/SYNCOPE-634
> Project: Syncope
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.2.2
> Reporter: Guido Wimmel
> Assignee: Guido Wimmel
> Priority: Minor
> Fix For: 1.2.3, 1.3.0
>
>
> As discussed on the dev mailing list [1]:
> On content loading from content.xml, before each insert, Syncope issues a
> database statement that reads the whole table content, only to get the table
> metadata (see ContentLoaderHandler.getParameters()).
> This can be optimized by adding "WHERE 0=1" to the query (so no records are
> returned, but the schema can still be obtained).
> [1]
> http://syncope-dev.1063484.n5.nabble.com/minor-optimization-for-content-loading-td5716645.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
