[Pypgsql-checkins] CVS: pypgsql README,1.31,1.32

[Billy G. A. <bal...@us...>]

Update of /cvsroot/pypgsql/pypgsql
In directory sc8-pr-cvs1:/tmp/cvs-serv7471

Modified Files:
	README 
Log Message:
14JUL2003 bga	Updated for release 2.4.


Index: README
===================================================================
RCS file: /cvsroot/pypgsql/pypgsql/README,v
retrieving revision 1.31
retrieving revision 1.32
diff -C2 -d -r1.31 -r1.32
*** README	10 Jul 2003 15:36:19 -0000	1.31
--- README	14 Jul 2003 21:35:57 -0000	1.32
***************
*** 2,6 ****
  
  ----------------------------------------------------------------------------
! pyPgSQL - v2.3: Python DB-API 2.0 Compliant Interface Module for PostgreSQL.
  ----------------------------------------------------------------------------
  ===============================
--- 2,6 ----
  
  ----------------------------------------------------------------------------
! pyPgSQL - v2.4: Python DB-API 2.0 Compliant Interface Module for PostgreSQL.
  ----------------------------------------------------------------------------
  ===============================
***************
*** 8,12 ****
  ===============================
  
!     pyPgSQL, version 2.3
      A Python DB-API 2.0 compliant interface for PostgreSQL
      Copyright 2000 by Billy G. Allie.
--- 8,12 ----
  ===============================
  
!     pyPgSQL, version 2.4
      A Python DB-API 2.0 compliant interface for PostgreSQL
      Copyright 2000 by Billy G. Allie.
***************
*** 1672,1677 ****
  When working with PostgreSQL large object, you MUST be in a transaction.
  The code will try to ensure that a transaction is active while working with
! 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.)
  
  ----------------------------------------------------------------------------
--- 1672,1683 ----
  When working with PostgreSQL large object, you MUST be in a transaction.
  The code will try to ensure that a transaction is active while working with
! large object (i.e. lo_open will start a transaction if necessary.)
! 
! ----------------------------------------------------------------------------
! 
! There is a change to the Connection.binary() function that *could* cause
! existing code to break.  Connection.binary() no longer commits the trans-
! action used to create the large object.  The application developer is now
! responsible for commiting (or rolling back) the transaction.
  
  ----------------------------------------------------------------------------