[Pypgsql-checkins] CVS: pypgsql README,1.25,1.26

[Gerhard H?r. <gha...@us...>]

Update of /cvsroot/pypgsql/pypgsql
In directory usw-pr-cvs1:/tmp/cvs-serv23256

Modified Files:
	README 
Log Message:
27OCT2002 gh  - Updates for 2.3b1.
              - Converted the whole document into reStructuredText, so we
                can easily built a HTML version using docutils
                (http://docutils.sf.net/).


Index: README
===================================================================
RCS file: /cvsroot/pypgsql/pypgsql/README,v
retrieving revision 1.25
retrieving revision 1.26
diff -C2 -d -r1.25 -r1.26
*** README	8 Sep 2002 16:17:19 -0000	1.25
--- README	27 Oct 2002 03:43:07 -0000	1.26
***************
*** 1,10 ****
! #ident "@(#) $Id$"
! pyPgSQL - v2.2: Python DB-API 2.0 Compliant Interface Module for PostgreSQL.
! ===========================================================================
  
  0. Copyright notice and License
  ===============================
  
!     pyPgSQL, version 2.2
      A Python DB-API 2.0 compliant interface for PostgreSQL
      Copyright 2000 by Billy G. Allie.
[...2724 lines suppressed...]
  
  When working with PostgreSQL large object, you MUST be in a transaction.
--- 1576,1585 ----
  a new transaction is created on the next call to execute().
  
  
  If a PostgreSQL array (represented by a Python list) is the only parameter to
! a query, then it must be passed in a singleton tuple.  For example::
  
!         cnx.query('insert into table values(%s)', (list,))
  
  
  When working with PostgreSQL large object, you MUST be in a transaction.
***************
*** 1392,1395 ****
  large object (i.e. lo_open will start a transaction if necessary.  lo_close
  will end the transaction if it determines that lo_open started one.)
- 
- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
--- 1587,1588 ----