Re: improving async support in psycopg

On 24/03/10 22:39, Tim Roberts wrote:
> Jan Urbański wrote:
>> I agree 100%. Let's start by designing an API then, although I don't
>> know anything about other databases, so I won't be able to tell if
>> similar things would be possible for MySQL or Oracle etc.
>
> Let us not lose sight of the fact that psycopg2 is intended to be an
> abstraction, based on a database-neutral standard (DBAPI 2).

> If someone wants to create a separate package that
> wraps the Postgres native API for Python in a direct and low-level way,
> that's fine, but it should not be part of psycopg2.  I should be able to
> take my psycopg2 application, replace the "psycopg2" instance with
> "pyMySQL", and have it Just Work.

Of course the default behaviour should not change, so existing 
application would continue to work. If you don't use the extentions, you 
won't ever see an async query. But I can't see anything wrong with 
exposing more native API, as long as it's optional and has no effect on 
people that are not willing to use it.

Cheers,
Jan
_______________________________________________
Psycopg mailing list
[email protected]
http://lists.initd.org/mailman/listinfo/psycopg