db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mpoes...@apache.org
Subject cvs commit: db-torque/xdocs postgres-howto.xml
Date Tue, 27 May 2003 16:36:29 GMT
mpoeschl    2003/05/27 09:36:29

  Modified:    xdocs    Tag: TORQUE_3_0_BRANCH postgres-howto.xml
  Log:
  sync with HEAD (rev. 1.6)
  
  Revision  Changes    Path
  No                   revision
  
  
  No                   revision
  
  
  1.4.4.1   +3 -3      db-torque/xdocs/postgres-howto.xml
  
  Index: postgres-howto.xml
  ===================================================================
  RCS file: /home/cvs/db-torque/xdocs/postgres-howto.xml,v
  retrieving revision 1.4
  retrieving revision 1.4.4.1
  diff -u -r1.4 -r1.4.4.1
  --- postgres-howto.xml	29 Nov 2001 01:39:30 -0000	1.4
  +++ postgres-howto.xml	27 May 2003 16:36:28 -0000	1.4.4.1
  @@ -13,7 +13,7 @@
   <p>
   Turbine comes with a default User implementation which utilizes some libraries,
   and code that are not 100% compatible with <a href="http://www.postgresql.org">
  -PostgreSQL</a>. This document will explain  what you need to get the defaut
  +PostgreSQL</a>. This document will explain  what you need to get the default
   Turbine User Implementation running with PostgreSQL. The user management code is
   only a small part of Turbine, and the default implementation is easily
   replacable. Rather than following the steps in this document, you can always
  @@ -42,8 +42,8 @@
   There is also a bug in the released versions of the PostgreSQL which causes
   problems when reading and writing Timestamps.  This is fixed in CVS.  So to
   run Turbine with PostgreSQL you need to get the latest JDBC driver code from
  -the PostgreSQL CVS server: :pserver:anoncvs@postgresql.org:/home/projects/pgsql/cvsroot
  -the password is postgresql.  Before compiling the driver though, you must apply
  +the PostgreSQL CVS server: :pserver:anoncvs@anoncvs.postgresql.org:/projects/cvsroot
  +(leave the password blank).  Before compiling the driver though, you must apply
   a patch so the metadata says that OID columns are java.sql.Types.VARBINARY, not
   java.sql.Types.INTEGER.  <strong>Important: If you need the metadata to report
   that OID columns are integers for another application, this patch will break
  
  
  

Mime
View raw message