psycopg news for 0.99.4
-----------------------

* psycopg is approaching 1.0, so only DBAPI compliance patches and bug fixes
  are getting in.

* added Binary and QuotedString objects. note that sometime before 1.0 we'll
  switch turn every string passed to psycopg into a QuotedString, possibily
  breaking Zope compatibility and old scripts doing their own quoting.

psycopg news for 0.5.x
----------------------

* this is the development branch, if you want stability, stick with 0.4.6.

* added pthread locks so that different threads (cursors) can use the same
  postgres connection (this was done *only* to respect the dbapi on cursor
  isolation.)

* now the default for the .cursor() method is to associate every cursor to
  the same physical connection, to avoid isolation (as the DBAPI-2.0 specify),
  you can change that by calling the .serialize() method on the connection and
  giving it 0 as the argument, e.g., "o.serialize(0)".

psycopg news for 0.4.1
----------------------

* autocommit mode is now supported on cursors and connections.

psycopg news for 0.4
--------------------

* implemented all the remaining DBAPI-2.0 type singletons (DATETIME and
  BINARY included)

psycopg news for 0.3
--------------------

* threading problems resolved

* added type casting from postgres to python (the user can now specify
  its own casting objects, the default singletons NUMBER and STRING are
  included [and act as default cast objects] plus INTEGER and FLOAT as
  an extension to the DBAPI-2.0.) 
  investigate the code in examples/usercast_test.py to understand how to
  add your own types...

* beginning of the Zope Database Adapter: give it a try even it it is 
  broken!
