Index: FAQ.html =================================================================== RCS file: /projects/cvsroot/pgsql-server/doc/src/FAQ/FAQ.html,v retrieving revision 1.167 diff -c -r1.167 FAQ.html *** FAQ.html 2003/02/14 14:03:10 1.167 --- FAQ.html 2003/02/14 21:25:02 *************** *** 245,252 ****

The database server can run on Windows NT and Win2k using Cygwin, the Cygnus Unix/NT porting library. See pgsql/doc/FAQ_MSWIN in the distribution or the MS Windows FAQ ! at ! http://www.PostgreSQL.org/docs/faq-mswin.html.

A native port to MS Win NT/2000/XP is currently being worked on.

--- 245,252 ----

The database server can run on Windows NT and Win2k using Cygwin, the Cygnus Unix/NT porting library. See pgsql/doc/FAQ_MSWIN in the distribution or the MS Windows FAQ ! at ! http://www.ca.PostgreSQL.org/docs/faq-mswin.html.

A native port to MS Win NT/2000/XP is currently being worked on.

*************** *** 535,541 ****

2.3) Does PostgreSQL have a graphical user interface?

! Yes, there are several graphical interfaces to PostgreSQL available. These include PgAccess http://www.pgaccess.org), PgAdmin II (http://www.pgadmin.org, --- 535,541 ----

2.3) Does PostgreSQL have a graphical user interface?

!

Yes, there are several graphical interfaces to PostgreSQL available. These include PgAccess http://www.pgaccess.org), PgAdmin II (http://www.pgadmin.org, *************** *** 545,552 **** http://www.thekompany.com/products/rekall/, proprietary). There is also PHPPgAdmin ( http://phppgadmin.sourceforge.net/ ), a web-based interface to ! PostgreSQL.

2.4) What languages are able to communicate with PostgreSQL?

--- 545,554 ---- http://www.thekompany.com/products/rekall/, proprietary). There is also PHPPgAdmin ( http://phppgadmin.sourceforge.net/ ), a web-based interface to ! PostgreSQL.

+

See http://techdocs.postgresql.org/guides/GUITools for a more detailed list.

+

2.4) What languages are able to communicate with PostgreSQL?

*************** *** 1037,1050 **** VARCHAR(n) varchar size specifies maximum length, no padding CHAR(n) bpchar blank padded to the specified fixed length TEXT text no specific upper limit on length - "char" char one character BYTEA bytea variable-length byte array (null-byte safe)

You will see the internal name when examining system catalogs and in some error messages.

!

The last four types above are "varlena" types (i.e., the first four bytes on disk are the length, followed by the data). Thus the actual space used is slightly greater than the declared size. However, these data types are also subject to compression or being --- 1039,1052 ---- VARCHAR(n) varchar size specifies maximum length, no padding CHAR(n) bpchar blank padded to the specified fixed length TEXT text no specific upper limit on length BYTEA bytea variable-length byte array (null-byte safe) + "char" char one character

You will see the internal name when examining system catalogs and in some error messages.

!

The first four types above are "varlena" types (i.e., the first four bytes on disk are the length, followed by the data). Thus the actual space used is slightly greater than the declared size. However, these data types are also subject to compression or being *************** *** 1058,1065 **** same length. CHAR(n) pads with blanks to the specified length, while VARCHAR(n) only stores the characters supplied. BYTEA is for storing binary data, ! particularly values that include NULL bytes. These ! types have similar performance characteristics.

4.15.1) How do I create a serial/auto-incrementing field?

--- 1060,1067 ---- same length. CHAR(n) pads with blanks to the specified length, while VARCHAR(n) only stores the characters supplied. BYTEA is for storing binary data, ! particularly values that include NULL bytes. All the ! types described here have similar performance characteristics.

4.15.1) How do I create a serial/auto-incrementing field?