Author: buildbot
Date: Wed May 7 08:54:15 2014
New Revision: 908291
Log:
Staging update by buildbot for olingo
Modified:
websites/staging/olingo/trunk/content/ (props changed)
websites/staging/olingo/trunk/content/doc/tutorials/Olingo_Tutorial_AdvancedRead_FilterVisitor.html
Propchange: websites/staging/olingo/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed May 7 08:54:15 2014
@@ -1 +1 @@
-1592948
+1592949
Modified:
websites/staging/olingo/trunk/content/doc/tutorials/Olingo_Tutorial_AdvancedRead_FilterVisitor.html
==============================================================================
---
websites/staging/olingo/trunk/content/doc/tutorials/Olingo_Tutorial_AdvancedRead_FilterVisitor.html
(original)
+++
websites/staging/olingo/trunk/content/doc/tutorials/Olingo_Tutorial_AdvancedRead_FilterVisitor.html
Wed May 7 08:54:15 2014
@@ -75,7 +75,7 @@
<h1 id="implementation-of-filter-visitor-jdbc">Implementation of
Filter Visitor (JDBC)</h1>
<h3
id="how-to-guide-for-implementing-a-filter-tree-transformation-into-a-jdbc-where-clause">How
To Guide for implementing a filter tree transformation into a JDBC where
clause</h3>
-<p>The query option $filter can be used to apply a filter query to the result
set. This tutorial will be about consuming and working with the filter tree
which an application will get from the OData Java library by implementing a
transformation of the filter expression into a JDBC where clause. The example
explained here will be kept simple to show the mechanism of the visitor
pattern. Security problem which occur when using user input (e.g. the filter
string of the URI) inside a where clause will be pointed out but not solved for
this tutorial. Knowledge about the visitor pattern is not necessary but
helpful. If you want to read further please refer to the further information
chapter at the end of this tutorial. All examples can be found as java sources
here.</p>
+<p>The query option $filter can be used to apply a filter query to the result
set. This tutorial will be about consuming and working with the filter tree
which an application will get from the OData Java library by implementing a
transformation of the filter expression into a JDBC where clause. The example
explained here will be kept simple to show the mechanism of the visitor
pattern. Security problem which occur when using user input (e.g. the filter
string of the URI) inside a where clause will be pointed out but not solved for
this tutorial. Knowledge about the visitor pattern is not necessary but
helpful. If you want to read further please refer to the further information
chapter at the end of this tutorial. All examples can be found as java sources
here: <a
href="http://olingo.apache.org/resources/test.jdbc.zip";>test.jdbc.zip</a></p>
<h3 id="examples">Examples</h3>
<h5 id="simple-example">Simple example</h5>
<p>If a filter expression is parsed by the OData library it will be
transformed into a filter tree. A simple tree for the expression âaâ eq
âbâ would look like this:</p>
