[Nepomuk] Review Request 111513: Use parameterized ODBC queries for adding statements

[Commit Hook]

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/111513/#review41445
-----------------------------------------------------------


This review has been submitted with commit ec5bbc2f89136f3473c715f066874ef90f429689 by Vishesh Handa to branch 2.9.

- Commit Hook


On July 15, 2013, 8:08 a.m., Sebastian Trueg wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> http://git.reviewboard.kde.org/r/111513/
> -----------------------------------------------------------
> 
> (Updated July 15, 2013, 8:08 a.m.)
> 
> 
> Review request for Nepomuk and Vishesh Handa.
> 
> 
> Repository: soprano
> 
> 
> Description
> -------
> 
> Soprano uses only plain query strings for all operations via ODBC (Virtuoso). However, parameterized queries can provide a much better performance, especially for long string values. This patch (available in branch feature/odbcParameterizedQueries) makes Soprano use parameterized queries for addStatement at least.
> 
> This should fix the memory leaking problem with adding large plain text blobs given that addStatement is used (AFAIK the Nepomuk indexer currently uses custom queries to add the data).
> 
> Should this patch proove to be effective it should be expanded to use parameterized queries wherever possible like removeStatement. Also using prepared ODBC queries could improve the performance considerably, especially when adding a large amount of statements.
> 
> 
> Diffs
> -----
> 
>   backends/virtuoso/odbcconnection.h c87bcb7 
>   backends/virtuoso/odbcconnection.cpp 754c76d 
>   backends/virtuoso/virtuosomodel.cpp a884703 
>   backends/virtuoso/virtuosomodel_p.h d5a86d8 
> 
> Diff: http://git.reviewboard.kde.org/r/111513/diff/
> 
> 
> Testing
> -------
> 
> Soprano tests run through smoothly. More performance and mem leakage testing needs to be done using Nepomuk.
> 
> 
> Thanks,
> 
> Sebastian Trueg
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/nepomuk/attachments/20131009/f77cdef4/attachment.html>