[QGIS Commit] r10208 - docs/trunk/english_us/user_guide

[svn_qgis at osgeo.org]

Author: gjm
Date: 2009-02-20 02:39:44 -0500 (Fri, 20 Feb 2009)
New Revision: 10208

Modified:
   docs/trunk/english_us/user_guide/plugins_writing_in_cpp.tex
   docs/trunk/english_us/user_guide/working_with_vector.tex
Log:
Add more details on how qgis deals with finding suitable key columns in views

Modified: docs/trunk/english_us/user_guide/plugins_writing_in_cpp.tex
===================================================================
--- docs/trunk/english_us/user_guide/plugins_writing_in_cpp.tex	2009-02-20 00:13:50 UTC (rev 10207)
+++ docs/trunk/english_us/user_guide/plugins_writing_in_cpp.tex	2009-02-20 07:39:44 UTC (rev 10208)
@@ -59,15 +59,15 @@
 \textbf{a) Create new pointconverter.pro file and add}:
 
 
-# 
-#
-# Note: the use of qmake / pro files for building plugins 
-# is outdated and the reader should be made aware that this 
-# chapter is not longer current. Tim will update this 
-# chapter in the near future, but in the meantime this
-# note serves as a reminder.
-#
-#
+%# 
+%#
+%# Note: the use of qmake / pro files for building plugins 
+%# is outdated and the reader should be made aware that this 
+%# chapter is not longer current. Tim will update this 
+%# chapter in the near future, but in the meantime this
+%# note serves as a reminder.
+%#
+%#
 
 
 \begin{verbatim}

Modified: docs/trunk/english_us/user_guide/working_with_vector.tex
===================================================================
--- docs/trunk/english_us/user_guide/working_with_vector.tex	2009-02-20 00:13:50 UTC (rev 10207)
+++ docs/trunk/english_us/user_guide/working_with_vector.tex	2009-02-20 07:39:44 UTC (rev 10208)
@@ -270,14 +270,21 @@
 column is indexed (note that primary keys are automatically indexed in
 PostgreSQL). 
 
-If the PostgreSQL layer is a view, the same requirements exists, but
+If the PostgreSQL layer is a view, the same requirement exists, but
 views don't have primary keys or columns with unique constraints on
 them. In this case QGIS will try to find a column in the view that is
-derived from a table column that is suitable. If one cannot be found,
-QGIS will not load the layer. If this occurs, the solution is to alter
-the view so that it does include a suitable column (a type of int4
-and either a primary key or with a unique constraint, preferably indexed).
+derived from a suitable table column. It does this by parsing the view
+definition SQL. However there are several aspects of SQL that QGIS ignores
+- these include the use of table aliases and columns that are generated by
+SQL functions.
 
+If a suitable column cannot be found, QGIS will not load the layer. If this
+occurs, the solution is to alter the view so that it does include a suitable
+column (a type of int4 and either a primary key or with a unique constraint,
+preferably indexed).
+
+When dealing with views, QGIS parses the view definition and
+
 \subsubsection{Importing Data into PostgreSQL}\label{sec:loading_postgis_data}
 \index{PostGIS!SPIT!importing data}