[DB-SIG] Preparing statement API

[Hrvoje Niksic]

"M.-A. Lemburg" <mal@lemburg.com> writes:

> > This was the specific intent behind the current design. An
> > unsophisticated provider (or database) need not worrying about
> > caching, reuse, preparation, or implementing additional
> > methods. The provider can add the reuse functionality and
> > performance will increase.

That's good design, and I tried to preserve it.  As I said, an
unsophisticated database can implement cursor.prepare() as
lambda x: x.  What you cannot do with the current API is have control
over whether a statement is cached.

> Therefore, I propose to add the new features I mentioned in a
> previous mail (cursor.command and cursor.prepare()) to the next
> release of the DB API spec.

Now that you've convinced me that it is meaningful to associate only
one statement to a cursor (at a time), I agree with your proposal.