From: Chris S. <c.s...@ar...> - 2005-01-19 08:16:11
|
hello, while testing postgresql 8 i was wondering if s.b. could provide some info if there are plans to finish an updated version of pypgsql which works with postgresql 8. thanks very much in advance. cheers chris |
From: Karsten H. <Kar...@gm...> - 2005-01-19 09:20:21
|
> while testing postgresql 8 i was wondering if s.b. could > provide some info if there are plans to finish an updated version > of pypgsql which works with postgresql 8. I assume you mean "takes advantage of the new binary protocol" ? I second that interest. Due to slow support (which may have very legitimate reasons) I have considered moving GnuMed to another DB-API module. Doing so will likely make our code more generic and thus switching back easier if later we ever so desire. We are already carrying a patch and a workaround in our CVS tree that apparently don't make it into pyPgSQL proper. A second patch is on the way in. All of them were posted on this list. PyPgSQL has served us well so far, however, including delivering NOTIFYs. Thanks, Karsten -- GPG key ID E4071346 @ wwwkeys.pgp.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346 |
From: jose <jo...@cy...> - 2005-01-19 17:25:57
|
If I've read this correctly the implication is that PyPgSQL is not = really going to be maintained any longer. Bummer really it is a very nice interface. If it is not going to be maintained, is there any recommendations as to which API to switch to? Jose -----Original Message----- From: pyp...@li... [mailto:pyp...@li...] On Behalf Of Karsten Hilbert Sent: Wednesday, January 19, 2005 1:11 AM To: pyp...@li... Subject: Re: [Pypgsql-users] pypgsql and postgresql 8 > while testing postgresql 8 i was wondering if s.b. could provide some=20 > info if there are plans to finish an updated version of pypgsql which=20 > works with postgresql 8. I assume you mean "takes advantage of the new binary protocol" ? I = second that interest. Due to slow support (which may have very legitimate reasons) I have considered moving GnuMed to another DB-API module. Doing so will likely = make our code more generic and thus switching back easier if later we ever so desire. We are already carrying a patch and a workaround in our CVS tree that apparently don't make it into pyPgSQL proper. A second patch is on = the way in. All of them were posted on this list. PyPgSQL has served us well so far, however, including delivering = NOTIFYs. Thanks, Karsten --=20 GPG key ID E4071346 @ wwwkeys.pgp.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346 ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and = FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Pypgsql-users mailing list Pyp...@li... https://lists.sourceforge.net/lists/listinfo/pypgsql-users |
From: Karsten H. <Kar...@gm...> - 2005-01-19 21:20:19
|
> If I've read this correctly the implication is that PyPgSQL is not really > going to be maintained any longer. STOP ! No ! I am just a user of PyPgSQL - same as the other people in this thread. I did not want to say that pyPgSQL won't be maintained any longer (I couldn't say that even if I wanted) but rather that to me maintenance has seemed OK but slow. I also said that there may be valid reasons for that. Karsten -- GPG key ID E4071346 @ wwwkeys.pgp.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346 |
From: jose <jo...@cy...> - 2005-01-19 21:35:55
|
Opps sorry for jumping to conclusions, I was really hoping that this was = in fact not the case, I think that is a great API and I would hate to see = it go away especially now that postgresql 8 is officially out Jose -----Original Message----- From: pyp...@li... [mailto:pyp...@li...] On Behalf Of Karsten Hilbert Sent: Wednesday, January 19, 2005 1:16 PM To: pyp...@li... Subject: Re: [Pypgsql-users] pypgsql and postgresql 8 > If I've read this correctly the implication is that PyPgSQL is not=20 > really going to be maintained any longer. STOP ! No ! I am just a user of PyPgSQL - same as the other people in this thread. I = did not want to say that pyPgSQL won't be maintained any longer (I couldn't = say that even if I wanted) but rather that to me maintenance has seemed OK = but slow. I also said that there may be valid reasons for that. Karsten --=20 GPG key ID E4071346 @ wwwkeys.pgp.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346 ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting = Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download = a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Pypgsql-users mailing list Pyp...@li... https://lists.sourceforge.net/lists/listinfo/pypgsql-users |
From: Karsten H. <Kar...@gm...> - 2005-01-19 22:00:19
|
> Opps sorry for jumping to conclusions, I was really hoping that this was in > fact not the case, I think that is a great API Well, it is written to the API specs set forth by the Python DB team. Which are lacking here and there, too, BTW. One thing that would be really good to know is whether and when pyPgSQL will support the out-of-band parameter passing. Or does it do so already ? (Not that I know.) Karsten -- GPG key ID E4071346 @ wwwkeys.pgp.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346 |
From: Michael H. <Mi...@Hi...> - 2005-01-19 22:11:37
|
Chris Schleiermacher wrote: > > while testing postgresql 8 i was wondering if s.b. could > provide some info if there are plans to finish an updated version > of pypgsql which works with postgresql 8. You didn't say what platform you're primarily interested in. If Win32, I've had good success using these binaries from Gerhard Häring: http://ghaering.de:9080/pypgsql/ Gerhard is a lead developer on pypgsql. I'm not using it on a *nix platform right now so I can't say about that. Michael |