Re: ZPsycoPGDA: How to contribute

On Tue, Jan 8, 2013 at 10:57 AM, Gaël Pegliasco
<gael.pegliasco@makina-corpus.com> wrote:

> Following my last post on this psycopg/ZPsycoPGDA ticket I wille be pleased
> to contribute to ZPyscopgDA development.

Thank you very much, and thank you again for your contributions to the
previous release.


> I just have created a post on my company blog trying to describe Zope
> Database Adaptaters (sorry for my poor english. Any typo comment is welcome,
> others too).
>
> If you allow me contributing to ZPsycopgDA, here are the points I would like
> to do:
>
> Adding documentation
> Adding unit tests

These would be very welcome.

> Implementing minor changes regarding my post above in db.py and Pool.py

I haven't found the details you refer to in the article...

> Maybe putting in comments Pool.py as it is not really required, except for
> its implementation of the *close* function which close all database
> connections and may be very usefull: default implementation only close
> database connection of the DB object of the thread executing the method (and
> not for all threads DB objects) - but I still have to check this before.

For any contribution you'd like to provide, you can fork the
ZPsycopgDA project on github, which is currently at the state of
psycopg 2.4.6. Provide the contributions you want into external
branches and I'll merge them back. As I've previously stated, the Zope
adapter may well benefit of a release cycle independent from psycopg.


> Also, I will be pleased to implement "bind variables" management in a
> similar way that the implementation I've recently worked on for ZcxoracleDA
> and that I will submit now to this project.

It sounds like prepared statements: they could be more generically
useful in psycopg too, not only in ZPsycopgDA. I have an experiment in
[1] but that's definitely not the only way to implement the same
concept (an useful one would be auto-preparation with LRU cache). I'd
like to first ask the DB-SIG if there is any idea about standardizing
a stored procedures interface.

[1] http://initd.org/psycopg/articles/2012/10/01/prepared-statements-psycopg/

Do you have an article or code showing what have you done for the
oracle adapter about bind variables?

Cheers,

-- Daniele