Update of /home/cvsd/slony1/slony1-engine/doc/adminguide
In directory main.slony.info:/tmp/cvs-serv21467

Modified Files:
	faq.sgml 
Log Message:
Add FAQ about use of "oid" column on replicable table


Index: faq.sgml
===================================================================
RCS file: /home/cvsd/slony1/slony1-engine/doc/adminguide/faq.sgml,v
retrieving revision 1.78
retrieving revision 1.79
diff -C2 -d -r1.78 -r1.79
*** faq.sgml	21 Apr 2008 21:32:56 -0000	1.78
--- faq.sgml	3 Oct 2008 16:41:23 -0000	1.79
***************
*** 428,431 ****
--- 428,454 ----
  </qandaentry>
  
+ <qandaentry>
+ <question> <para> My application uses OID attributes; is it possible to replicate tables like this? </para>
+ </question>
+ 
+ <answer><para> It is worth noting that oids, as a regular table
+ attribute, have been deprecated since &postgres; version 8.1, back in
+ 2005.  &slony1; has <emphasis>never</emphasis> collected oids to
+ replicate them, and, with that functionality being deprecated, the
+ developers do not intend to add this functionality. </para>
+ 
+ <para> &postgres; implemented oids as a way to link its internal
+ system tables together; to use them with application tables is
+ considered <emphasis>poor practice</emphasis>, and it is recommended
+ that you use sequences to populate your own ID column on application
+ tables.  </para> </answer>
+ 
+ <answer><para> Of course, nothing prevents you from creating a table
+ <emphasis>without</emphasis> oids, and then add in your own
+ application column called <envar>oid</envar>, preferably with type
+ information <command>SERIAL NOT NULL UNIQUE</command>, which
+ <emphasis>can</emphasis> be replicated, and which is likely to be
+ suitable as a candidate primary key for the table. </para> </answer>
+ 
  </qandadiv>