[PyGreSQL] Re: PyGreSQL 3.0

[Stephan Richter]

>Mostly the DB-SIG API but ftp://ftp.druid.net/pub/distrib/PyGreSQL-beta.tgz
>has a Changelog with all the changes.

Very nice. The NULL -> None was one of the other things which came up 
frequently. Looks very promising! :)

> > I am really in need for the following to make PostGres work better with 
> Zope:
> >
> > - DateTime fields are returned as DateTime objects
>
>I'm thinking of using mxDateTime for this since it is necessary for the
>new API anyway.

Yeah, I know. That would be cool and save a lot of frustration on my side. 
:) The DateTime handling causes about 80% of my errors when writing code, 
since some translation from a string to a DateTime object does not work right.

> > - thread safety
>
>I have some patches for this which may go in before release.

I really hope so. I really think that would make the entire Zope+Postgres 
story much more stable. I know that many people use Zope + Postgres (which 
requires PyGres). I always suggest PostGres as the free DB of choice.

> > I saw that someone else started writing another Python product that uses
> > the new DB API to connect to PostGres. Did you look at his stuff at all?
>
>No.  Have you got a URL?

http://starship.python.net/crew/cjr/

>BTW, I really would prefer discussing on the mailing list.  You can join
>at http://www.vex.net/mailman/listingo/pygresql.

I am on since quiet a while now, but stayed silent. :)

Regards,
Stephan
--
Stephan Richter - (901) 573-3308 - srichter at cbu.edu
CBU - Physics & Chemistry; Framework Web - Web Design & Development
PGP Key: 735E C61E 5C64 F430 4F9C 798E DCA2 07E3 E42B 5391