Accepted cl-pg 1:20061216-1 (source all)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Tue,  6 Feb 2007 10:32:28 +0100
Source: cl-pg
Binary: cl-pg
Architecture: source all
Version: 1:20061216-1
Distribution: experimental
Urgency: low
Maintainer: Peter Van Eynde <pvaneynd@debian.org>
Changed-By: Peter Van Eynde <pvaneynd@debian.org>
Description: 
 cl-pg      - Common Lisp library that provides a socket level postgresql inter
Changes: 
 cl-pg (1:20061216-1) experimental; urgency=low
 .
   * New upstream. Major changes:
 .
      + Don't flush the network stream in SEND-PACKET, because it slows down
      API calls that have multiple SEND-PACKET calls in them. From
      attila.lendvai@gmail.com.
 .
      + Fix numeric parser for negative numbers. From
      levente.meszaros@gmail.com
 .
      + Make sure we consume the ReadyForQuery packet that is generated when
      closing a prepared statement or portal, or the packet can be
      misinterpreted by a later query, leading to data loss. Fix from Robert J.
      Macomber.
 .
      + Add an ABORT keyword argument to PG-DISCONNECT (from Robert J.
      Macomber <pgsql@rojoma.com>), as per CL:CLOSE.
 .
       "I've run into a problem with pg-disconnect if something abnormal
       happens to the database connection -- if the database goes away for a
       restart while pg has a connection open, for example.  When this
       happens, pg-disconnect fails, and the socket file descriptor is left
       open (presumably for a finalizer to clean up), also raising a new
       error from the unwind-protect in with-pg-connection.  To guard against
       the possibility, I've added an :abort parameter to pg-disconnect, like
       cl:close has, and made with-pg-connection call it with :abort t if the
       body exits abnormally, in the same way that with-open-file operates.
       When :abort is true, the modified pg-disconnect closes the database
       connection ungracefully, including making the close call abort
       (otherwise, sbcl at keast tries to flush the stream, raising another
       error if the database isn't there anymore)."
 .
      + Allow encoding used for socket communication with the backend to be
      specified as a keyword argument to PG-CONNECT, for cases where rebinding
      *PG-CLIENT-ENCODING* is inconvenient.
 .
      Add a simple test for encoding support.
 .
      (From Attila Lendvai <attila.lendvai@gmail.com>)
   * upload to experimental during the freeze
Files: 
 8e9901fe3851b5907448c83cce21e9b1 671 devel optional cl-pg_20061216-1.dsc
 5b1623aba7921c3d1e4ad6e770cf2b2d 48887 devel optional cl-pg_20061216.orig.tar.gz
 5864d06e280c23250089199079269cf3 6924 devel optional cl-pg_20061216-1.diff.gz
 c32ff3d10d0d23caa4d4d739f2b0d107 46528 devel optional cl-pg_20061216-1_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFFyEsx11ldN0tyliURAme1AJ0fFj06S9aZPiJilS92ybbceoqRzACfSaaL
ATkkOTWXkCnnCRZJOpMlI6Y=
=tF8D
-----END PGP SIGNATURE-----


Accepted:
cl-pg_20061216-1.diff.gz
  to pool/main/c/cl-pg/cl-pg_20061216-1.diff.gz
cl-pg_20061216-1.dsc
  to pool/main/c/cl-pg/cl-pg_20061216-1.dsc
cl-pg_20061216-1_all.deb
  to pool/main/c/cl-pg/cl-pg_20061216-1_all.deb
cl-pg_20061216.orig.tar.gz
  to pool/main/c/cl-pg/cl-pg_20061216.orig.tar.gz