# HG changeset patch
# User Tim Englich <tim.englich@intevation.de>
# Date 1273496824 0
# Node ID c53a39cb780910789e1989f71126374ab71d891d
# Parent  7a8f9eb9fb040480a119e951cb975601d06f5353
Moved section Query-configuration to Section Model of Transitions.

doc/trunk@1085 c6561f87-3c4e-4783-a992-168aeb5c3f6f

diff -r 7a8f9eb9fb04 -r c53a39cb7809 doc/ChangeLog
--- a/doc/ChangeLog	Mon May 10 12:53:17 2010 +0000
+++ b/doc/ChangeLog	Mon May 10 13:07:04 2010 +0000
@@ -1,3 +1,9 @@
+2010-05-10  Tim Englich  <tim@intevation.de>
+
+	* config-manual/model_of_transitions.tex,
+	  config-manual/general_settings.tex:
+	Moved section Query-configuration to Section Model of Transitions.
+
 2010-05-10  Tim Englich  <tim@intevation.de>
 
 	* config-manual/model_of_transitions.tex:
diff -r 7a8f9eb9fb04 -r c53a39cb7809 doc/config-manual/general_settings.tex
--- a/doc/config-manual/general_settings.tex	Mon May 10 12:53:17 2010 +0000
+++ b/doc/config-manual/general_settings.tex	Mon May 10 13:07:04 2010 +0000
@@ -106,32 +106,6 @@
 These Section configures the Artifacts which could be reached using the Artifact-Server.
 The meaning of artifacts are explained in Section TODO: LINK to Model of Transition
 
-
-
-\paragraph{Query-configuration (queries.properties)}
-
-This File contains Key-Value-Pairs to define SQL-Statements.
-All Queries will be handle using the Prepared-Statement-Syntax using "?"
-to define an Place where an dynamic Value should be placed into the Statement.
-
-There is one special Implementation to support spatial access to the ArcSDE,
-because the ArcSDE does not support the Access to spatial Objects using the
-definition of the Simple Feature Specification for SQL of the OGC.
-
-It was necessary to implement this mechanism to simulate the Access.
-
-All Queries which contains the following Literals will be handle separate
-using the ArcSDE-API.
-
-\begin{itemize}
-    \item ST\_ASTEXT(SHAPE): Will return the Geometry as an WellKnowText (WKT)
-    \item ST\_ASTEXT(RASTER): Will return the Raster in an readable Way.
-    \item INTERSECTS(SHAPE,"?"): Will only return the Elements which Geometry
-                                 intersects the given Geometry ("?" will be 
-                                 replace with an WKT) 
-\end{itemize}
-
-\subsection{Logging}
 \subsection{Configure ArtifactServer using Systemproperties}
 \begin{itemize}
     \item artifact.database.dir The folder where the Configuration is located-
diff -r 7a8f9eb9fb04 -r c53a39cb7809 doc/config-manual/model_of_transitions.tex
--- a/doc/config-manual/model_of_transitions.tex	Mon May 10 12:53:17 2010 +0000
+++ b/doc/config-manual/model_of_transitions.tex	Mon May 10 13:07:04 2010 +0000
@@ -455,6 +455,35 @@
 ORDER BY m.ZLOCATION DESC
 \end{lstlisting}
 
+The queries which are shown above are configurable.
+You can do this in the file {\tt queries.properties } which will
+be explained in the next paragraph.
+
+\paragraph{Query-configuration (queries.properties)}
+
+This file contains key-value-pairs to define SQL-statements.
+All queries will be handle using the prepared-statement-syntax using "?"
+to define a place where an dynamic value should be placed into the statement.
+ 
+There is one special implementation to support spatial access to the 
+{\tt ArcSDE}, because the {\tt ArcSDE} does not support the access to 
+spatial objects using the definition of the Simple Feature Specification for 
+SQL of the OGC.
+
+It was necessary to implement this mechanism to realize the access to spatial-
+objects.
+
+All queries which contains the following literals will be handle separate
+using the {\tt ArcSDE-API}.
+
+\begin{itemize}
+    \item {\tt ST\_ASTEXT(SHAPE)}: Will return the geometry as an WellKnowText (WKT)
+    \item {\tt ST\_ASTEXT(RASTER)}: Will return the raster in an readable way.
+    \item {\tt INTERSECTS(SHAPE,"?")}: Will only return the elements which geometry
+                                 intersects the given geometry ("?" will be
+                                 replace with an WKT)
+\end{itemize}
+
 
 \paragraph{Transitions}