head	1.21;
access;
symbols
	REL9_0_0:1.20.2.1
	REL9_1_ALPHA1:1.21
	REL9_0_RC1:1.20.2.1
	REL9_0_BETA4:1.20
	REL9_0_STABLE:1.20.0.2
	REL9_0_BETA3:1.20
	REL9_0_BETA2:1.19
	REL8_0_25:1.7
	REL8_1_21:1.9
	REL8_2_17:1.14.2.2
	REL8_3_11:1.19
	REL8_4_4:1.19
	REL9_0_BETA1:1.19
	REL9_0_ALPHA5_BRANCH:1.19.0.14
	REL9_0_ALPHA5:1.19
	REL8_0_24:1.7
	REL8_1_20:1.9
	REL8_2_16:1.14.2.2
	REL8_3_10:1.19
	REL8_4_3:1.19
	REL9_0_ALPHA4:1.19
	REL9_0_ALPHA4_BRANCH:1.19.0.12
	REL8_5_ALPHA3:1.19
	REL8_5_ALPHA3_BRANCH:1.19.0.10
	REL8_0_23:1.7
	REL8_1_19:1.9
	REL8_2_15:1.14.2.2
	REL8_3_9:1.19
	REL8_4_2:1.19
	REL8_5_ALPHA2:1.19
	REL8_5_ALPHA2_BRANCH:1.19.0.8
	REL8_0_22:1.7
	REL8_1_18:1.9
	REL8_2_14:1.14.2.2
	REL8_3_8:1.19
	REL8_4_1:1.19
	REL8_5_ALPHA1:1.19
	REL8_5_ALPHA1_BRANCH:1.19.0.6
	REL8_4_STABLE:1.19.0.4
	REL8_4_0:1.19
	REL8_4_RC2:1.19
	REL8_4_RC1:1.19
	REL8_4_BETA2:1.19
	REL8_4_BETA1:1.19
	REL8_0_21:1.7
	REL8_1_17:1.9
	REL8_2_13:1.14.2.2
	REL8_3_7:1.19
	REL8_0_20:1.7
	REL8_1_16:1.9
	REL8_2_12:1.14.2.2
	REL8_3_6:1.19
	REL8_0_19:1.7
	REL8_1_15:1.9
	REL8_2_11:1.14.2.2
	REL8_3_5:1.19
	REL8_0_18:1.7
	REL8_1_14:1.9
	REL8_2_10:1.14.2.2
	REL8_3_4:1.19
	REL8_0_17:1.7
	REL8_1_13:1.9
	REL8_2_9:1.14.2.2
	REL8_3_3:1.19
	REL8_0_16:1.7
	REL8_1_12:1.9
	REL8_2_8:1.14.2.2
	REL8_3_2:1.19
	REL8_2_7:1.14.2.1
	REL8_3_1:1.19
	REL8_3_STABLE:1.19.0.2
	REL8_3_0:1.19
	REL8_3_RC2:1.19
	REL8_0_15:1.7
	REL8_1_11:1.9
	REL8_2_6:1.14.2.1
	REL8_3_RC1:1.19
	REL8_3_BETA4:1.19
	REL8_3_BETA3:1.19
	REL8_3_BETA2:1.18
	REL8_3_BETA1:1.16
	REL8_0_14:1.7
	REL8_1_10:1.9
	REL8_2_5:1.14.2.1
	REL8_0_13:1.7
	REL8_1_9:1.9
	REL8_2_4:1.14
	REL8_0_12:1.7
	REL8_1_8:1.9
	REL8_2_3:1.14
	REL8_0_11:1.7
	REL8_1_7:1.9
	REL8_2_2:1.14
	REL8_0_10:1.7
	REL8_1_6:1.9
	REL8_2_1:1.14
	REL8_2_STABLE:1.14.0.2
	REL8_2_0:1.14
	REL8_2_RC1:1.14
	REL8_2_BETA3:1.13
	REL8_2_BETA2:1.13
	REL8_1_5:1.9
	REL8_0_9:1.7
	REL8_2_BETA1:1.13
	REL8_0_8:1.7
	REL8_1_4:1.9
	REL8_0_7:1.7
	REL8_1_3:1.9
	REL8_0_6:1.7
	REL8_1_2:1.9
	REL8_0_5:1.7
	REL8_1_1:1.9
	REL8_1_STABLE:1.9.0.2
	REL8_1_0:1.9
	REL8_1_0RC1:1.9
	REL8_1_0BETA4:1.9
	REL8_1_0BETA3:1.9
	REL8_0_4:1.7
	REL8_1_0BETA2:1.9
	REL8_1_0BETA1:1.9
	REL8_0_3:1.7
	REL8_0_2:1.7
	REL8_0_1:1.7
	REL8_0_STABLE:1.7.0.4
	REL8_0_0:1.7.0.2
	REL8_0_0RC5:1.7
	REL8_0_0RC4:1.7
	REL8_0_0RC3:1.7
	REL8_0_0RC2:1.5
	REL8_0_0RC1:1.4;
locks; strict;
comment	@# @;


1.21
date	2010.08.17.04.37.20;	author petere;	state Exp;
branches;
next	1.20;

1.20
date	2010.06.07.02.01.08;	author itagaki;	state Exp;
branches
	1.20.2.1;
next	1.19;

1.19
date	2007.11.14.01.58.18;	author tgl;	state Exp;
branches;
next	1.18;

1.18
date	2007.10.16.19.04.34;	author mha;	state Exp;
branches;
next	1.17;

1.17
date	2007.10.16.12.14.33;	author mha;	state Exp;
branches;
next	1.16;

1.16
date	2007.05.03.15.47.48;	author alvherre;	state Exp;
branches;
next	1.15;

1.15
date	2007.01.31.20.56.17;	author momjian;	state Exp;
branches;
next	1.14;

1.14
date	2006.11.20.17.42.16;	author neilc;	state Exp;
branches
	1.14.2.1;
next	1.13;

1.13
date	2006.09.16.00.30.13;	author momjian;	state Exp;
branches;
next	1.12;

1.12
date	2006.08.01.19.17.18;	author alvherre;	state Exp;
branches;
next	1.11;

1.11
date	2006.08.01.00.09.06;	author momjian;	state Exp;
branches;
next	1.10;

1.10
date	2006.03.10.19.10.47;	author momjian;	state Exp;
branches;
next	1.9;

1.9
date	2005.04.09.03.52.43;	author momjian;	state Exp;
branches;
next	1.8;

1.8
date	2005.03.31.03.54.38;	author momjian;	state Exp;
branches;
next	1.7;

1.7
date	2004.12.29.23.36.46;	author tgl;	state Exp;
branches;
next	1.6;

1.6
date	2004.12.28.22.47.15;	author tgl;	state Exp;
branches;
next	1.5;

1.5
date	2004.12.13.18.05.08;	author petere;	state Exp;
branches;
next	1.4;

1.4
date	2004.12.03.06.30.40;	author momjian;	state Exp;
branches;
next	1.3;

1.3
date	2004.12.03.06.18.12;	author momjian;	state Exp;
branches;
next	1.2;

1.2
date	2004.12.03.06.04.38;	author momjian;	state Exp;
branches;
next	1.1;

1.1
date	2004.12.03.05.50.17;	author momjian;	state Exp;
branches;
next	;

1.14.2.1
date	2007.05.03.15.47.37;	author alvherre;	state Exp;
branches;
next	1.14.2.2;

1.14.2.2
date	2008.05.29.02.01.07;	author momjian;	state Exp;
branches;
next	;

1.20.2.1
date	2010.08.17.04.37.16;	author petere;	state Exp;
branches;
next	;


desc
@@


1.21
log
@Spell and markup checking
@
text
@<!-- $PostgreSQL: pgsql/doc/src/sgml/external-projects.sgml,v 1.20 2010/06/07 02:01:08 itagaki Exp $ -->

 <appendix id="external-projects">
  <title>External Projects</title>

  <para>
   <productname>PostgreSQL</productname> is a complex software project,
   and managing the project is difficult. We have found that many
   enhancements to <productname>PostgreSQL</productname> can be more
   efficiently developed separately from the core project.
  </para>

  <para>
   To help our community with the development of their external projects, we
   have created <ulink url="http://www.pgfoundry.org/">PgFoundry</ulink>, a
   website that provides hosting for <productname>PostgreSQL</>-related
   projects that are maintained outside the core <productname>PostgreSQL</>
   distribution. PgFoundry is built using the GForge software project and is
   similar to <ulink url="http://sourceforge.net">SourceForge.net</> in its
   feature set, providing mailing lists, forums, bug tracking, CVS, and web
   hosting. If you have a <productname>PostgreSQL</>-related open source
   project that you would like to have hosted at PgFoundy, please feel free
   to create a new project.
  </para>

 <sect1 id="external-interfaces">
  <title>Client Interfaces</title>

  <indexterm>
   <primary>interfaces</primary>
   <secondary>externally maintained</secondary>
  </indexterm>

  <para>
   There are only two client interfaces included in the base
   <productname>PostgreSQL</productname> distribution:
   <itemizedlist>
    <listitem>
     <para>
      <link linkend="libpq">libpq</link> is included because it is the
      primary C language interface, and because many other client interfaces
      are built on top of it.
     </para>
    </listitem>

    <listitem>
     <para>
      <link linkend="ecpg">ECPG</link> is included because it depends on the
      server-side SQL grammar, and is therefore sensitive to changes in
      <productname>PostgreSQL</productname> itself.
     </para>
    </listitem>
   </itemizedlist>

   All other language interfaces are external projects and are distributed
   separately. <xref linkend="language-interface-table"> includes a list of
   some of these projects. Note that some of these packages might not be
   released under the same license as <productname>PostgreSQL</>. For more
   information on each language interface, including licensing terms, refer to
   its website and documentation.
  </para>

  <table id="language-interface-table">
   <title>Externally Maintained Client Interfaces</>

   <tgroup cols="4">
    <thead>
     <row>
      <entry>Name</entry>
      <entry>Language</entry>
      <entry>Comments</entry>
      <entry>Website</entry>
     </row>
    </thead>

    <tbody>
     <row>
      <entry>DBD::Pg</entry>
      <entry>Perl</entry>
      <entry>Perl DBI driver</entry>
      <entry><ulink url="http://search.cpan.org/dist/DBD-Pg/">http://search.cpan.org/dist/DBD-Pg/</ulink></entry>
     </row>

     <row>
      <entry>JDBC</entry>
      <entry>JDBC</entry>
      <entry>Type 4 JDBC driver</entry>
      <entry><ulink url="http://jdbc.postgresql.org/">http://jdbc.postgresql.org/</ulink></entry>
     </row>

     <row>
      <entry>libpqxx</entry>
      <entry>C++</entry>
      <entry>New-style C++ interface</entry>
      <entry><ulink url="http://pqxx.org/">http://pqxx.org/</ulink></entry>
     </row>

     <row>
      <entry>Npgsql</entry>
      <entry>.NET</entry>
      <entry>.NET data provider</entry>
      <entry><ulink url="http://npgsql.projects.postgresql.org/">http://npgsql.projects.postgresql.org/</ulink></entry>
     </row>

     <row>
      <entry>ODBCng</entry>
      <entry>ODBC</entry>
      <entry>An alternative ODBC driver</entry>
      <entry><ulink url="http://projects.commandprompt.com/public/odbcng/">http://projects.commandprompt.com/public/odbcng/</ulink></entry>
     </row>

     <row>
      <entry>pgtclng</entry>
      <entry>Tcl</entry>
      <entry></entry>
      <entry><ulink url="http://pgfoundry.org/projects/pgtclng/">http://pgfoundry.org/projects/pgtclng/</ulink></entry>
     </row>

     <row>
      <entry>psqlODBC</entry>
      <entry>ODBC</entry>
      <entry>The most commonly-used ODBC driver</entry>
      <entry><ulink url="http://psqlodbc.projects.postgresql.org/">http://psqlodbc.projects.postgresql.org/</ulink></entry>
     </row>

     <row>
      <entry>psycopg</entry>
      <entry>Python</entry>
      <entry>DB API 2.0-compliant</entry>
      <entry><ulink url="http://www.initd.org/">http://www.initd.org/</ulink></entry>
     </row>
    </tbody>
   </tgroup>
  </table>
 </sect1>

 <sect1 id="external-pl">
  <title>Procedural Languages</title>

  <indexterm>
   <primary>procedural language</primary>
   <secondary>externally maintained</secondary>
  </indexterm>

  <para>
   <productname>PostgreSQL</productname> includes several procedural
   languages with the base distribution: <link
   linkend="plpgsql">PL/PgSQL</link>, <link linkend="pltcl">PL/Tcl</link>,
   <link linkend="plperl">PL/Perl</link>, and <link
   linkend="plpython">PL/Python</link>.
  </para>

  <para>
   In addition, there are a number of procedural languages that are developed
   and maintained outside the core <productname>PostgreSQL</productname>
   distribution. <xref linkend="pl-language-table"> lists some of these
   packages. Note that some of these projects might not be released under the same
   license as <productname>PostgreSQL</>. For more information on each
   procedural language, including licensing information, refer to its website
   and documentation.
  </para>

  <table id="pl-language-table">
   <title>Externally Maintained Procedural Languages</title>

   <tgroup cols="3">
    <thead>
     <row>
      <entry>Name</entry>
      <entry>Language</entry>
      <entry>Website</entry>
     </row>
    </thead>

    <tbody>
     <row>
      <entry>PL/Java</entry>
      <entry>Java</entry>
      <entry><ulink url="http://pljava.projects.postgresql.org/">http://pljava.projects.postgresql.org/</ulink></entry>
     </row>

     <row>
      <entry>PL/PHP</entry>
      <entry>PHP</entry>
      <entry><ulink url="http://www.commandprompt.com/community/plphp/">http://www.commandprompt.com/community/plphp/</ulink></entry>
     </row>

     <row>
      <entry>PL/Py</entry>
      <entry>Python</entry>
      <entry><ulink url="http://python.projects.postgresql.org/">http://python.projects.postgresql.org/</ulink></entry>
     </row>

     <row>
      <entry>PL/R</entry>
      <entry>R</entry>
      <entry><ulink url="http://www.joeconway.com/plr/">http://www.joeconway.com/plr/</ulink></entry>
     </row>

     <row>
      <entry>PL/Ruby</entry>
      <entry>Ruby</entry>
      <entry><ulink url="http://raa.ruby-lang.org/project/pl-ruby/">http://raa.ruby-lang.org/project/pl-ruby/</ulink></entry>
     </row>

     <row>
      <entry>PL/Scheme</entry>
      <entry>Scheme</entry>
      <entry><ulink url="http://plscheme.projects.postgresql.org/">http://plscheme.projects.postgresql.org/</ulink></entry>
     </row>

     <row>
      <entry>PL/sh</entry>
      <entry>Unix shell</entry>
      <entry><ulink url="http://plsh.projects.postgresql.org/">http://plsh.projects.postgresql.org/</ulink></entry>
     </row>
    </tbody>
   </tgroup>
  </table>
 </sect1>
 
 <sect1 id="external-extensions">
 <title>Extensions</title>

  <indexterm>
   <primary>extensions</primary>
  </indexterm>

  <para>
   <productname>PostgreSQL</> is designed to be easily extensible. For
   this reason, extensions loaded into the database can function just
   like features that are packaged with the database. The
   <filename>contrib/</> directory shipped with the source code
   contains a large number of extensions. The <filename>README</> file
   in that directory contains a summary. They include conversion
   tools, full-text indexing, <acronym>XML</> tools, and additional
   data types and indexing methods. Other extensions are developed
   independently, like <application><ulink
   url="http://www.postgis.org/">PostGIS</ulink></>.  Even
   <productname>PostgreSQL</> replication solutions are developed
   externally. For example, <application> <ulink
   url="http://www.slony.info">Slony-I</ulink></> is a popular
   master/standby replication solution that is developed independently
   from the core project.
  </para>

  <para>
   There are several administration tools available for
   <productname>PostgreSQL</>. The most popular is
   <application><ulink url="http://www.pgadmin.org/">pgAdmin III</ulink></>, 
   and there are several commercially available ones as well.
  </para>
 </sect1>
</appendix>
@


1.20
log
@Replace "slave" to "standby" in documentation for consistent terminology.
Almost all of the terms in docs and messages were replaced, but still
remains in a few comments and README files in codes.
@
text
@d1 1
a1 1
<!-- $PostgreSQL: pgsql/doc/src/sgml/external-projects.sgml,v 1.19 2007/11/14 01:58:18 tgl Exp $ -->
d48 1
a48 1
      <link linkend="ecpg">ecpg</link> is included because it depends on the
@


1.20.2.1
log
@Spell and markup checking
@
text
@d1 1
a1 1
<!-- $PostgreSQL: pgsql/doc/src/sgml/external-projects.sgml,v 1.20 2010/06/07 02:01:08 itagaki Exp $ -->
d48 1
a48 1
      <link linkend="ecpg">ECPG</link> is included because it depends on the
@


1.19
log
@Clean up some now-obsolete references to GBorg.
@
text
@d1 1
a1 1
<!-- $PostgreSQL: pgsql/doc/src/sgml/external-projects.sgml,v 1.18 2007/10/16 19:04:34 mha Exp $ -->
d243 1
a243 1
   master/slave replication solution that is developed independently
@


1.18
log
@Fix the URL properly per Robert Treat.
@
text
@d1 1
a1 1
<!-- $PostgreSQL: pgsql/doc/src/sgml/external-projects.sgml,v 1.17 2007/10/16 12:14:33 mha Exp $ -->
a25 14
  <note>
   <para>
    Many <productname>PostgreSQL</productname>-related projects are still
    hosted at <ulink url="http://gborg.postgresql.org/">GBorg</>.  GBorg is
    the original external community developer site, and while it is
    currently closed to new projects in favor of PgFoundry, it still
    contains many active and relevant projects. Other popular
    <productname>PostgreSQL</productname>-related projects are hosted
    independently, or on other project-hosting sites such as <ulink
    url="http://sourceforge.net/">SourceForge.net</ulink>. You should search
    the web if you don't find the project you are looking for.
   </para>
  </note>

a98 7
      <entry>libpq++</entry>
      <entry>C++</entry>
      <entry>Old-style C++ interface</entry>
      <entry><ulink url="http://gborg.postgresql.org/project/libpqpp/">http://gborg.postgresql.org/project/libpqpp/</ulink></entry>
     </row>

     <row>
@


1.17
log
@Update URLs to a couple of external projects
@
text
@d1 1
a1 1
<!-- $PostgreSQL: pgsql/doc/src/sgml/external-projects.sgml,v 1.16 2007/05/03 15:47:48 alvherre Exp $ -->
d109 1
a109 1
      <entry><ulink url="http://pqxx.tk/">http://pqxx.tk/</ulink></entry>
@


1.16
log
@Fix a few more double words in docs.
@
text
@d1 1
a1 1
<!-- $PostgreSQL: pgsql/doc/src/sgml/external-projects.sgml,v 1.15 2007/01/31 20:56:17 momjian Exp $ -->
d109 1
a109 1
      <entry><ulink url="http://thaiopensource.org/development/libpqxx/">http://thaiopensource.org/development/libpqxx/</ulink></entry>
d123 1
a123 1
      <entry><ulink url="http://pgfoundry.org/projects/npgsql/">http://pgfoundry.org/projects/npgsql/</ulink></entry>
d144 1
a144 1
      <entry><ulink url="http://odbc.postgresql.org/">http://odbc.postgresql.org/</ulink></entry>
@


1.15
log
@Update documentation on may/can/might:

Standard English uses "may", "can", and "might" in different ways:

        may - permission, "You may borrow my rake."

        can - ability, "I can lift that log."

        might - possibility, "It might rain today."

Unfortunately, in conversational English, their use is often mixed, as
in, "You may use this variable to do X", when in fact, "can" is a better
choice.  Similarly, "It may crash" is better stated, "It might crash".

Also update two error messages mentioned in the documenation to match.
@
text
@d1 1
a1 1
<!-- $PostgreSQL: pgsql/doc/src/sgml/external-projects.sgml,v 1.14 2006/11/20 17:42:16 neilc Exp $ -->
d34 1
a34 1
    independently, or on other project-hosting sites such such as <ulink
@


1.14
log
@Overhaul the "External Projects" chapter in the manual. Replace
the variabelist with a more concise table, add a URL for each project,
remove some orphaned projects, add PL/Py, and various other changes.
Initial patch from Robert Treat, subsequent work by Neil Conway.
@
text
@d1 1
a1 1
<!-- $PostgreSQL: pgsql/doc/src/sgml/external-projects.sgml,v 1.13 2006/09/16 00:30:13 momjian Exp $ -->
d71 1
a71 1
   some of these projects. Note that some of these packages may not be
d178 1
a178 1
   packages. Note that some of these projects may not be released under the same
@


1.14.2.1
log
@Fix a few more double words in docs.
@
text
@d1 1
a1 1
<!-- $PostgreSQL: pgsql/doc/src/sgml/external-projects.sgml,v 1.14 2006/11/20 17:42:16 neilc Exp $ -->
d34 1
a34 1
    independently, or on other project-hosting sites such as <ulink
@


1.14.2.2
log
@Update odbc URL.
@
text
@d1 1
a1 1
<!-- $PostgreSQL: pgsql/doc/src/sgml/external-projects.sgml,v 1.14.2.1 2007/05/03 15:47:37 alvherre Exp $ -->
d144 1
a144 1
      <entry><ulink url="http://psqlodbc.projects.postgresql.org/">http://psqlodbc.projects.postgresql.org/</ulink></entry>
@


1.13
log
@Remove emacs info from footer of SGML files.
@
text
@d1 1
a1 1
<!-- $PostgreSQL: pgsql/doc/src/sgml/external-projects.sgml,v 1.12 2006/08/01 19:17:18 alvherre Exp $ -->
d4 1
a4 1
  <title>PgFoundry and External Projects</title>
d10 1
a10 1
   efficiently developed separately from the core project. 
d12 1
a12 1
  
d14 10
a23 7
   To help our community with the development of their external projects,
   we have created the <ulink url="http://www.pgfoundry.org/">PgFoundry</ulink>.
   <ulink url="http://www.pgfoundry.org/">PgFoundry</ulink> is built using the
   GForge software project and is similar to SourceForge in its feature set. If
   you have a PostgreSQL related Open Source project that you would like to 
   develop and need project management resources such as mailing lists, forums,
   bug tracking, and CVS, please feel free to create a new project.   
d26 22
d49 26
a74 8
   Secondly, many <productname>PostgreSQL</productname>-related projects are
   still hosted at <ulink url="http://gborg.postgresql.org/"><productname>GBorg</></ulink>. 
   GBorg is the original external community developer site, and while it is 
   currently closed to new projects in favor of PgFoundry, it still contains 
   many active and relevant projects. There are other popular <productname>PostgreSQL</productname> 
   related projects that are hosted independently as well at other community 
   sites such as <ulink url="http://www.sf.net/">SourceForge</ulink>. You should 
   search the web if you don't find the project you are looking for.
d77 83
a159 2
 <sect1 id="external-interfaces">
  <title>Externally Developed Interfaces</title>
d162 2
a163 1
   <primary>interfaces</primary>
d167 19
a185 94
   <productname>PostgreSQL</productname> includes very few interfaces
   with the base distribution. <application>libpq</> is packaged because
   it is the primary <application>C</> interface and many other interfaces
   are build on top of it.  <application>ecpg</> is also packaged because it is
   tied to the server-side grammar so is very dependent on the database
   version. All the other interfaces, such as ODBC, Java, Perl, Python, and
   others, are external projects and must be installed separately.
  </para>

  <para>
   Some of the more popular interfaces are:

   <variablelist>
    <varlistentry>
     <term>psqlODBC</term>
     <listitem>
      <para>
       This is the most common interface for <application>Windows</>
       applications. <ulink url="http://odbc.postgresql.org/">Website.</ulink>
      </para>
     </listitem>
    </varlistentry>

    <varlistentry>
     <term>ODBCng</term>
     <listitem>
      <para>
       Another ODBC driver for PostgreSQL. 
       <ulink url="http://projects.commandprompt.com/public/odbcng/">Website.</ulink>
      </para>
     </listitem>
    </varlistentry>

    <varlistentry>
     <term>PostgreSQL JDBC Driver</term>
     <listitem>
      <para>
       A <application>JDBC</> interface.
       <ulink url="http://jdbc.postgresql.org/">Website.</ulink>
      </para>
     </listitem>
    </varlistentry>

    <varlistentry>
     <term>Npgsql</term>
     <listitem>
      <para>
       <application>.Net</> data provider for <application>C#</> applications.
       <ulink url="http://pgfoundry.org/projects/npgsql/">Website.</ulink>
      </para>
     </listitem>
    </varlistentry>

    <varlistentry>
     <term>libpqxx</term>
     <listitem>
      <para>
       A <application>C++</> interface.
       <ulink url="http://thaiopensource.org/development/libpqxx/">Website.</ulink>
      </para>
     </listitem>
    </varlistentry>

    <varlistentry>
     <term>DBD::Pg</term>
     <listitem>
      <para>
       A <application>Perl</> DBI driver for PostgreSQL.
       <ulink url="http://search.cpan.org/dist/DBD-Pg/">Website.</ulink>
      </para>
     </listitem>
    </varlistentry>

    <varlistentry>
     <term>pgtclng</term>
     <listitem>
      <para>
       A <application>Tcl</> interface.
       <ulink url="http://gborg.postgresql.org/project/pgtclng/projdisplay.php">Website.</ulink>
      </para>
     </listitem>
    </varlistentry>

    <varlistentry>
     <term>pyscopg</term>
     <listitem>
      <para>
       A <application>Python</> interface library that is DB API 2.0 compliant.
       <ulink url="http://www.initd.org/">Website.</ulink>
      </para>
     </listitem>
    </varlistentry>
   </variablelist>
   </para>
d187 54
d251 3
a253 3
   <productname>PostgreSQL</> was designed from the start to be
   extensible. For this reason, extensions loaded into the database can
   function just like features that are packaged with the database. The
d256 10
a265 7
   in that directory contains a summary. They include conversion tools,
   full-text indexing, <acronym>XML</> tools, and additional data types
   and indexing methods. Other extensions are developed independently,
   like <application>PostGIS</>. Even <application>PostgreSQL</>
   replication solutions are developed externally. For example,
   <application>Slony-I</> is a popular master/slave replication solution
   that is developed independently from the core project.
d273 1
a273 2
  </para> 

@


1.12
log
@Editorialize a bit on the recent patch, reverting to the original versions
of the text where appropiate.
@
text
@d1 1
a1 1
<!-- $PostgreSQL: pgsql/doc/src/sgml/external-projects.sgml,v 1.11 2006/08/01 00:09:06 momjian Exp $ -->
a169 17

<!-- Keep this comment at the end of the file
Local variables:
mode:sgml
sgml-omittag:nil
sgml-shorttag:t
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:1
sgml-indent-data:t
sgml-parent-document:nil
sgml-default-dtd-file:"./reference.ced"
sgml-exposed-tags:nil
sgml-local-catalogs:("/usr/lib/sgml/catalog")
sgml-local-ecat-files:nil
End:
-->
@


1.11
log
@Improvements to Maintenance and External Projects documentation.

Joshua D. Drake
Robert Treat
@
text
@d1 1
a1 1
<!-- $PostgreSQL: pgsql/doc/src/sgml/external-projects.sgml,v 1.10 2006/03/10 19:10:47 momjian Exp $ -->
d25 1
a25 1
   still hosted at <ulink url="http://gborg.postgresql.org"><productname>GBorg</></ulink>. 
d30 2
a31 2
   sites such as <ulink url="http://www.sf.net">SourceForge</ulink>. You should 
   google if you don't find the project you are looking for.
d44 5
a48 4
   it is the primary dependecy of most interfaces available to PostgreSQL.
   We also package <application>ecpg</> because it is tied to the 
   server-side grammar. All other interfaces, such as PHP, Perl, Python,
   and Ruby, are external projects.
d76 1
a76 1
     <term>pgjdbc</term>
d89 1
a89 1
       <application>.Net</> interface for more recent <application>mono/C#</> applications.
d99 1
a99 1
       A newer <application>C++</> interface.
d119 1
a119 1
       A newer version of the <application>Tcl</> interface.
d126 1
a126 1
     <term>Pyscopg</term>
@


1.10
log
@Make $PostgreSQL CVS tags consistent for SGML files.
@
text
@d1 1
a1 1
<!-- $PostgreSQL: pgsql/doc/src/sgml/advanced.sgml,v 1.49 2005/04/09 03:52:43 momjian Exp $ -->
d4 1
a4 1
  <title>External Projects</title>
d8 1
a8 1
   and managing it is difficult. We have found that many
d10 11
a20 8
   efficiently developed separately from the core project. Separate
   projects can
   have their own developer teams, email lists, bug tracking,
   and release schedules. While their independence makes
   development easier, it makes users' jobs harder. They have to hunt
   around looking for database enhancements to meet their needs.
   This section describes some of the more popular externally
   developed enhancements and guides you on how to find them.
d24 8
a31 6
   Many <productname>PostgreSQL</productname>-related projects are
   hosted at either 
   <ulink url="http://gborg.postgresql.org"><productname>GBorg</></ulink>
   or <ulink url="http://pgfoundry.org"><productname>pgFoundry</></ulink>.
   There are other <productname>PostgreSQL</productname>-related projects that are hosted
   elsewhere, but you will have to do an Internet search to find them.
d44 4
a47 5
   it is the primary <application>C</> interface and many other
   interfaces are built on top of it. <application>ecpg</> is packaged
   because it is tied to the server-side grammar so is very dependent
   on the database version. All the other interfaces are independent
   projects and must be installed separately.
d59 1
a59 1
       applications.
d65 1
a65 1
     <term>pgjdbc</term>
d68 2
a69 1
       A <application>JDBC</> interface.
d75 1
a75 1
     <term>Npgsql</term>
d78 2
a79 2
       <application>.Net</> interface for more recent
       <application>Windows</> applications.
d85 1
a85 1
     <term>libpqxx</term>
d88 2
a89 1
       A newer <application>C++</> interface.
d95 1
a95 1
     <term>libpq++</term>
d98 2
a99 11
       An older <application>C++</> interface.
      </para>
     </listitem>
    </varlistentry>

    <varlistentry>
     <term>pgperl</term>
     <listitem>
      <para>
       A <application>Perl</> interface with an <acronym>API</> similar
       to <application>libpq</>.
d105 1
a105 1
     <term>DBD-Pg</term>
d108 2
a109 2
       A <application>Perl</> interface that uses the
       <acronym>DBD</>-standard <application>API</>.
d119 1
d125 1
a125 10
     <term>pgtcl</term>
     <listitem>
      <para>
       The original version of the <application>Tcl</> interface.
      </para>
     </listitem>
    </varlistentry>

    <varlistentry>
     <term>PyGreSQL</term>
d128 2
a129 1
       A <application>Python</> interface library.
a132 1

a133 4

   All of these can be found at
   <ulink url="http://gborg.postgresql.org"><productname>GBorg</></ulink>
   or <ulink url="http://pgfoundry.org"><productname>pgFoundry</></ulink>.
d163 2
a164 2
   <application>pgAdmin</>, and there are several commercially
   available ones.
@


1.9
log
@We don't put URL's in ulink's because the URL is always generated, but
we can put words in ulink and the URL will still be printed.

per Peter
@
text
@d1 1
a1 3
<!--
$PostgreSQL: pgsql/doc/src/sgml/external-projects.sgml,v 1.8 2005/03/31 03:54:38 momjian Exp $
-->
@


1.8
log
@Adjust SGML ulink tags to the URL is always displayed in our printed docs.
@
text
@d2 1
a2 1
$PostgreSQL: pgsql/doc/src/sgml/external-projects.sgml,v 1.7 2004/12/29 23:36:46 tgl Exp $
d24 4
a27 6
   hosted at either <productname>GBorg</> at <ulink
   url="http://gborg.postgresql.org"></ulink>
   or <productname>pgFoundry</> at <ulink
   url="http://pgfoundry.org"></ulink>.
   There are other
   <productname>PostgreSQL</productname>-related projects that are hosted
d148 3
a150 5
   All of these can be found at 
   <productname>GBorg</> (<ulink
   url="http://gborg.postgresql.org"></ulink>)
   or <productname>pgFoundry</> (<ulink
   url="http://pgfoundry.org"></ulink>).
@


1.7
log
@Convert external-projects to an appendix.
@
text
@d2 1
a2 1
$PostgreSQL: pgsql/doc/src/sgml/external-projects.sgml,v 1.6 2004/12/28 22:47:15 tgl Exp $
d24 2
a25 3
   hosted at either
   <productname>GBorg</> at <ulink
   url="http://gborg.postgresql.org">http://gborg.postgresql.org</ulink>
d27 1
a27 1
   url="http://pgfoundry.org">http://pgfoundry.org</ulink>.
d152 1
a152 1
   url="http://gborg.postgresql.org">http://gborg.postgresql.org</ulink>)
d154 1
a154 1
   url="http://pgfoundry.org">http://pgfoundry.org</ulink>).
@


1.6
log
@More minor updates and copy-editing.
@
text
@d2 1
a2 1
$PostgreSQL: pgsql/doc/src/sgml/external-projects.sgml,v 1.5 2004/12/13 18:05:08 petere Exp $
d5 1
a5 1
 <chapter id="external-projects">
d25 3
a27 3
   <productname>GBorg</> at <ulink url="http://gborg.postgresql.org">
   http://gborg.postgresql.org</ulink> or
   <productname>pgFoundry</> at <ulink
d34 1
a34 1
 <sect1 id="interfaces">
d150 6
d160 1
a160 1
 <sect1 id="extensions">
d190 1
a190 1
</chapter>
@


1.5
log
@Spell checker run
@
text
@d2 1
a2 1
$PostgreSQL: pgsql/doc/src/sgml/external-projects.sgml,v 1.4 2004/12/03 06:30:40 momjian Exp $
d12 5
a16 4
   efficiently developed independently of the main project. They can
   have their own developer teams, email lists, their own bug tracking,
   and their own release schedule. While their independence makes
   development easier, it makes user's jobs harder. They have to hunt
d18 1
a18 1
   This section outlines some of the more popular externally
d22 12
d52 1
a52 5
   To use other interfaces, you have to do some searching. For example,
   <productname>GBorg</> at <ulink url="http://gborg.postgresql.org">
   http://gborg.postgresql.org</ulink> has over thirty interfaces listed
   in its <literal>Drivers/Interfaces</> section. Some of the more
   popular interfaces are:
d66 9
d85 1
a85 1
     <term>libpq++</term>
d88 1
a88 1
       An older <application>C++</> interface.
d94 1
a94 1
     <term>libpqxx</term>
d97 1
a97 1
       A newer <application>C++</> interface.
d123 1
a123 1
     <term>pgtcl</term>
d126 1
a126 1
       The original version of the <application>TCL</> interface.
d132 1
a132 1
     <term>PyGreSQL</term>
d135 1
a135 1
       A <application>Python</> interface library.
d141 1
a141 1
     <term>pgjdbc</term>
d144 1
a144 10
       A <application>JDBC</> interface.
      </para>
     </listitem>
    </varlistentry>

    <varlistentry>
     <term>pgtclng</term>
     <listitem>
      <para>
       A newer version of the <application>TCL</> interface.
a151 8
  <para>
   That section also contains several server-side languages that are
   separate projects. <application>pgFoundry</> at <ulink
   url="http://pgfoundry.org">http://pgfoundry.org</ulink> contains
   even more projects. Other projects are not even hosted on these
   servers and you will have to do an Internet search to find them.
  </para>

d173 1
a173 1
   that is developed independently from the main projects.
@


1.4
log
@Typo fixes.
@
text
@d2 1
a2 1
$PostgreSQL: pgsql/doc/src/sgml/external-projects.sgml,v 1.3 2004/12/03 06:18:12 momjian Exp $
a46 10
     <term>ODBC</term>
     <listitem>
      <para>
       This is the most common interface for <application>Windows</>
       applications.
      </para>
     </listitem>
    </varlistentry>

    <varlistentry>
d148 1
a148 1
   servers and you will have to do an internet search to find them.
d164 1
a164 1
   <filename>/contrib</> directory shipped with the source code
d171 1
a171 1
   <application>Slony</> is a popular master/slave replication solution
d178 1
a178 1
   <application>pgadmin</>, and there are several commercially
@


1.3
log
@Fix typo.
@
text
@d2 1
a2 1
$PostgreSQL: pgsql/doc/src/sgml/external-projects.sgml,v 1.2 2004/12/03 06:04:38 momjian Exp $
d9 9
a17 13
   <productname>PostgreSQL</productname> is a large piece of very
   complex software, and managing the code is a difficult process. We
   have found that many enhancements to
   <productname>PostgreSQL</productname> can be more efficiently
   developed independently of the main project. They can have their own
   developer teams, email lists, their own bug tracking, and their own
   release schedule. While their independence makes development easier,
   it makes users job harder. They have to hunt around looking for
   database enhancements to meet their needs.
  </para>

  <para>
   This section will outlines some of the more popular externally
d29 1
a29 1
   <productname>PostgreSQL</productname> packages very few interfaces
d33 1
a33 1
   because it is tied to the server-side grammar so it is very dependent
d35 1
a35 1
   projects.
@


1.2
log
@Merge pgadmin paragraph.
@
text
@d2 1
a2 1
$PostgreSQL: pgsql/doc/src/sgml/external-projects.sgml,v 1.1 2004/12/03 05:50:17 momjian Exp $
d179 1
a179 1
   contains a large number of extensions. The <filename>READMD</> file
@


1.1
log
@First version of external projects manual section.
@
text
@d2 1
a2 1
$PostgreSQL: pgsql/doc/src/sgml/external-projects.sgml,v 1.170 2004/12/02 15:32:52 momjian Exp $
a188 9
 </sect1>

 <sect1 id="administration-tools">
 <title>Administration Tools</title>

  <indexterm>
   <primary>administration tools</primary>
  </indexterm>

@

