[DB-SIG] spec: named parameters: clarification needed
Marcos Sánchez Provencio
msanchez@grupoburke.com
18 Feb 2003 20:39:21 +0100
El mar, 18-02-2003 a las 15:51, Anthony Tuininga escribió:
> On Tue, 2003-02-18 at 06:44, Marcos Sánchez Provencio wrote:
> > I was thinking more about vampirising (?) mx.ODBC extensions API and
> > using them as an API specification. Even M.-A. has proposed that some
> > time, I think.
> >
> > I am not sure we need yet-another-layer. The minimal to get whatever th=
e
> > RDBMS gives us to Python DBAPI is enough for me. That is, after we
> > clarify parameter passing and schema funtions ;-)
>
> But therein lies the problem. Every database vendor does this slightly
> differently. There is going to __have__ to be a layer in between the
> database and the Python DB API standard -- either it will be written
> once (a common layer) or many times (a layer written by each driver
> developer excepting those who write for database vendors that mimic the
> standard). Personally, I would prefer once.... :-)
What is the magical way to write it once?