You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@syncope.apache.org by "Guido Wimmel (JIRA)" <ji...@apache.org> on 2015/02/10 12:00:35 UTC

[jira] [Resolved] (SYNCOPE-634) performance optimization for content loading

     [ https://issues.apache.org/jira/browse/SYNCOPE-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guido Wimmel resolved SYNCOPE-634.
----------------------------------
    Resolution: Fixed

> 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)