On 2007-05-22 16:16, Carsten Haese wrote:
> This has been discussed before, but I'd like to re-cast
a vote on this
> for DB-API 3.0:
>
> * Deprecate/disallow pyformat/format paramstyles.
+0
> * Make qmark the mandatory minimum paramstyle. Allowing
additional
> parameter styles (numeric and/or named) would be
optional and
> implementation specific.
+1
Just an aside:
Note that the named style allows binding the same parameter
more than once.
This poses a few problems for interfaces which
rely on the database telling the interface how to best bind
a parameter, since it may well be that case that a
parameter
needs to be bound as e.g. integer in one place (e.g. as
index)
and float in another (e.g. if used in a formula).
For numbers, it's fairly obvious what to do (create
multiple
bindings for the object), but it's not for objects that
don't
easily allow retrieving the same value twice, such as
iterators or files.
I don't know how interfaces that do support named style
deal
with this problem.
--
Marc-Andre Lemburg
eGenix.com
Professional Python Services directly from the Source (#1,
May 23 2007)
>>> Python/Zope Consulting and Support ...
http://www.egenix.com/
>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/
>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/
____________________________________________________________
____________
:::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,MacOSX for
free ! ::::
eGenix.com Software, Skills and Services GmbH
Pastor-Loeh-Str.48
D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre
Lemburg
Registered at Amtsgericht Duesseldorf: HRB 46611
_______________________________________________
DB-SIG maillist - DB-SIG python.org
http:/
/mail.python.org/mailman/listinfo/db-sig
|
