Log Message:
-----------
It wasn't clear to a Gentle Reader that TRUNCATE is not a statement which
Slony-I can replicate automatically.  Modifying intro.sgml to indicate
this as being a limitation.

Modified Files:
--------------
    slony1-engine/doc/adminguide:
        intro.sgml (r1.22 -> r1.23)

-------------- next part --------------
Index: intro.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/intro.sgml,v
retrieving revision 1.22
retrieving revision 1.23
diff -Ldoc/adminguide/intro.sgml -Ldoc/adminguide/intro.sgml -u -w -r1.22 -r1.23
--- doc/adminguide/intro.sgml
+++ doc/adminguide/intro.sgml
@@ -136,11 +136,11 @@
 <para>&slony1; does not automatically propagate schema changes, nor
 does it have any ability to replicate large objects.  There is a
 single common reason for these limitations, namely that &slony1;
-collects updates using triggers, and neither schema changes nor large
-object operations are able to triggers suitable to inform &slony1;
-when those sorts of changes take place.  As a result, the only
-database objects where &slony1; can replicate updates are tables and
-sequences.  </para>
+collects updates using triggers, and neither schema changes, large
+object operations, nor <command>TRUNCATE</command> requests are able
+to triggers suitable to inform &slony1; when those sorts of changes
+take place.  As a result, the only database objects where &slony1; can
+replicate updates are tables and sequences.  </para>
 
 <para> Note that with the <emphasis>use</emphasis> of triggers comes
 some additional <emphasis>fiddling around with triggers</emphasis>.